Comment by _puk
21 hours ago
Not to make everything about AI, but..
The current analogy I am using when vibe coding is it's like defragging a hard drive in terms of time wasted.
Years of sitting there as the bar crept closer to 99 in the vain hope I could turn the computer off and go to bed, just to have to sit there for another hour or so until finished.
So many late nights wasted doing, I'm not sure what.
And now I'm sat there waiting for the agent to come back..
Running for 17m.. "dealing with a complex response"..
Codex (GPT5.6) has me hooked on that loop moreso as it is, in practice, so much quicker than Claude (Opus or Fable), so I don't quite ever walk away.
Nostalgia.
What actually triggered me to do that was to be able to test repeatably my other open source project in rust were the compile target directory can go to hundreds of gigabytes of files and at the same time I need to benchmark it on large linear slabs we do create for memory mapped files and I definitely noted the impact. I can only guess but non-optimal extent length create a repeated round trip to the metadata in main memory instead of "linear reads" (as consecutive logical numbers) + maybe the fact that those SSD are probably super smart and prefetch the next sectors? (see the jitter numbers I get even on a slow device in other comments)
poetic :)