Hacker News new | past | comments | ask | show | jobs | submit login

I'm still trying to figure that out :)

Here are some ideas:

• Debugging: figuring out why a variable or object property has an unexpected value

• Finding relevant code, possibly during onboarding of new devs

• Security: see where insecure values end up at runtime

• Telling BE devs what endpoint is used for a specific part of the UI

The architecture could also enable a few other features, like pausing when a particular value is encountered anywhere in the code.




Finding relevant code, possibly during onboarding of new devs

That one is huge for me. So often coming into a new codebase (especially in the case where some of the libraries or underlying frameworks are new to me) I just want to know "How the F was that value populated??"

Kudos, would be super useful in my opinion.


I can already imagine the dev tool improvements that could come from something like this.

Being able to highlight a part of the dom and click through the stack of where it came from would be awesome! And it would work with just about any framework out there!


> new devs

By the time you're no longer a "new dev," you're a "new dev" to the code you wrote when you started the job :) so it's a pretty universal need!




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: