Ask HN: How do you read, sign off, verify, manage the volume of generated slop?

2 pointsby throwaway11837 hours ago4 comments

ceejayoz7 hours ago
> 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?
verdverm7 hours ago
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
- throwaway11835 hours ago
  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
  - verdverm5 hours ago
    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
blinkbat7 hours ago
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.
- throwaway11837 hours ago
  But how are you scoping the features these days? Unlike back in the day, these days a feature is equivalent of research paper
  - verdverm7 hours ago
    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
    throwaway11835 hours ago
    Yeah this over engineering is really annoying bit
damian133 hours ago
[flagged]