2 points | by throwaway1183 5 hours ago ago
9 comments
> However, for those who have to read 2000 lines of code every single hour, how are you managing the mental bandwidth?
Do you really think that's what's happening?
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
why are you even attempting to read 2000 loc per hour? that won't work.
if ai generated the code, ai can review it. I can review perhaps pieces that are deemed priority. manual and automated testing are both required.
for the rest, please number your Qs so they're easy to address.
But how are you scoping the features these days? Unlike back in the day, these days a feature is equivalent of research paper
if you prompt differently, you can instruct them to work on small things
they have a strong tendency to over engineer (volume), prompt against this - in permanent files like AGENTS.md or per-session in follow on messages
Yeah this over engineering is really annoying bit
[flagged]
> However, for those who have to read 2000 lines of code every single hour, how are you managing the mental bandwidth?
Do you really think that's what's happening?
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
why are you even attempting to read 2000 loc per hour? that won't work.
if ai generated the code, ai can review it. I can review perhaps pieces that are deemed priority. manual and automated testing are both required.
for the rest, please number your Qs so they're easy to address.
But how are you scoping the features these days? Unlike back in the day, these days a feature is equivalent of research paper
if you prompt differently, you can instruct them to work on small things
they have a strong tendency to over engineer (volume), prompt against this - in permanent files like AGENTS.md or per-session in follow on messages
Yeah this over engineering is really annoying bit
[flagged]