Most of programming productivity is finding ways to reduce the iteration cycle. Live coding > linting > compile warnings > tests > usage.
Related Posts
I'm experimenting with live-evaluating tests in my programming language project.
It's relatively fiddly to hook up a UI for this, but it saves a precious keystroke to run the tests! I'm hoping that it results in more, better tests due to the convenience.
Is there a programming equivalent of the strawberry problem, i.e. a specific coding task that LLMs are consistently bad at?
I'm still experimenting with UIs for live (sandboxed) evaluation of tests. I've realised that you really want to highlight the failing assertion, not just the failing test.
Feedback welcome :)