Darklang is exploring an IDE experience where you have values you can inspect as you write code. It does this by tracing recent requests and autorunning pure code.
It's neat! Seeing concrete values is a definite usability win.
https://medium.com/darklang/building-an-office-sign-in-in-dark-c2d980560695
Related Posts
Over a sufficiently long time horizon, all code you write is legacy code.
It's really satisfying to use a profiler for the first time on a project. I always find a big performance win with only a small code change.
It's never the code that I expected to be slow, however!
I'm intrigued to see that Google has quantified that new code is generally buggier and less secure than code that has existed in your codebase for longer: https://security.googleblog.com/2024/09/eliminating-memory-safety-vulnerabilities-Android.html