Hacker News Reader

staying in the loop and being methodical about it (at least trying)

I more often find the walls of markdown to be more onerous than the code changes

would you mind sharing how you reduce it. I am testing hacks like asking to draw in block diagrams, write like RFC, write like algo and pseudocode

context engineering, with guidelines drawn from examples in my own projects

more up front planning, in a markdown file, multiple sessions

review processes, for the plan and then the code

the "recursive self improvement" (at the harness/context engineering level) feels like it is starting to kick in