r/codereview • u/javinpaul • 4h ago
r/codereview • u/SquashHot4348 • 5h ago
Functional Ever wondered what happens inside your code? ๐คฏ
Ever wondered what happens inside your code? ๐คฏ
You write a solution, hit Run, and see Accepted.
Great! ๐
But have you ever stopped and wondered what actually happened between those lines of code?
- How did your variables change at every step?
- What happened inside the call stack?
- How did your array, heap, or hash map evolve?
- What exactly happens when a recursive function calls itself?
I've often found myself wanting to see these things instead of just reading through the code or manually debugging every step.
So, I decided to build something around that idea.
Meet AlgoLens โก
It's a code visualizer + debugger built for people solving LeetCode problems.
The idea is simple: Don't just execute your code. Visualize how it works.
With AlgoLens, you can:
- ๐ Trace your code step by step.
- ๐ฏ Highlight the currently executing line.
- ๐งฉ Track variable changes and call-stack activity.
- ๐ณ Visualize recursion.
- ๐ป Work with Python, Java, C++ and JavaScript.
I've also tried to make it feel a little more interactive โ almost like turning the debugging process into a game. ๐ฎ
Want to try it?
AlgoLens is currently available as a free Microsoft Edge extension:
๐ https://microsoftedge.microsoft.com/addons/detail/jhhkkpabkoeaiajdilomalbmjdppcmcc
Don't use Edge? No problem!
You can also use it on chrome -> Watch video for reference[ AlgoLens - chrome ]
I'm still developing and improving it, so I'd genuinely appreciate feedback.
One thing I'd love to know: What's the one thing you wish you could visualize while solving a LeetCode problem?
Would love to hear your thoughts! ๐
r/codereview • u/It-Guy-2026 • 4h ago
True+True = 2 !!! ๐คฃ
Started learning C++ and knew that in programming "true + true = 2" actually.
r/codereview • u/Bisuta3 • 4h ago
Python Building in public isn't always about big wins. Today, 56 forks and 3 GitHub achievements made my day.
r/codereview • u/Ok-Committee5924 • 7h ago
Claude Code Is Designed to Make You Dumb
reddit.comr/codereview • u/Ok-Committee5924 • 7h ago
Claude code is design to make you dump
reddit.comr/codereview • u/yellow-llama1 • 14h ago
Maintain velocity without sacrificing reliability!
github.comCoding agents can modify code across multiple repositories, but reviewing the impact on dependencies and architecture is still difficult.
We've built an open-source tool, enola, that detects dependency cycles, layer violations, and structural regressions introduced by code changes.
It also lets agents track code symbols across refactors usingย enola locate, so stored references can be checked for changes.
In our benchmark, Claude Opus 5.5 answered 18/20 cross-repository architecture questions correctly with enola, compared with 4/20 without it.
GitHub:ย https://github.com/enola-labs/enola
It can run in the CI as an additional validation step.
How are you reviewing architectural impact when agents modify large codebases? How do you keep up with the increased velocity?