Hoi hoi!
I’m @nyaomaru, a frontend engineer currently fighting the intense European heatwave by building DIY window screens here in the Netherland...
For further actions, you may consider blocking this person and/or reporting abuse
Stepping backward through the timeline is the feature that would've saved me hours on LeetCode, since the place I lose the thread is always mid-loop, not at the end. Quick one on the internals, does the runtime handle recursion like DFS on a tree where each frame has its own copy of the locals? That's exactly where "watch the state change" tools usually fall apart, and if you nailed it that's the killer case.
Thanks for the nice question! 😸
The short answer is almost "yes", with one caveat.
Recursive calls run as real JavaScript calls, so each DFS invocation has its own parameters and local variables. At every recorded step, DSA View View deep-clones the variables visible at that execution point and records the logical call stack.
When you step backward, it selects an earlier snapshot rather than trying to reverse the execution itself. The recursion view also reconstructs the call depth and tracks the arguments and return value of each call.
The current limitation is that it doesn’t yet provide a "debugger-style view" showing the local variables of every suspended frame at the same time. The Variables panel currently reflects the selected execution step.
So DFS itself works, but the full per-frame locals UI is still one of the gaps I’d like to close. Recursive bugs are already confusing enough without the tool hiding half the stack 😅
I’ve created an issue for this feature and will work on it 👇
github.com/nyaomaru/dsa-view-view/...
Thank you for pointing out such an important use case! 👍
thank you for sharing!
The F1 analogy landed for me. I hit exactly this last month building a video pipeline: my motion stage was silently falling back to static frames because it couldn't load an fp8 model. No crash, no traceback — the pipeline reported success on every scene. If I hadn't understood what was happening underneath, I'd have shipped a hundred "working" videos with no motion in them.
That's the part AI-assisted speed doesn't save you from: a graceful fallback is a great place for bugs to hide, and you can only find them if you understand the layer below.
Also — stepping backward through the timeline is the right call. The place you lose the thread is always mid-loop.
Nice catch! I’m really glad you found it before shipping a hundred “working” videos with no motion 😅
That example perfectly shows the danger of graceful fallbacks. The pipeline can report success while silently producing the wrong result.
AI can help us implement things faster, but that doesn’t automatically make the implementation correct. I think humans still need to understand the layers underneath, verify the behavior, and take responsibility for that correctness.
And I’m really happy the mid-loop point resonated with you! That exact moment where you lose the thread is what I wanted DSA View View to make visible. 😸
Nice work!
Thank you! Please enjoy coding 😸
Nice 👍
Thx! Have a nice coding 👍
nice
Thx!
Thanks for sharing, nice idea!
Thank you for nice comment 😸
cool, star-ed it :)
Thanks!! That made me really happy 😸 Happy coding!
this is pretty awesome! bravo!
Thx! Have a nice coding! 😸
Great work!
Thank you! 😸