[mdale]

Was spending a lot with cursor switching between sonnet and opus 4.1s like 1500 to $2k a month. Was doing a lot of tabs in parallel of course. Output was like 5k lines on Good day. (Lines not the best measurement) But a yard stick against feature testing and rework.

Now with gpt-5-codex and codex vs code ext .. getting through up to 20k line changes in a day again lots of parallel jobs; but codex allows for less rework.

The job of the "engineer" has changed a lot. At 5k lines I was not reviewing every detail but it was possible to skim over what had changed. At 20k it's more looking at logs performance / arch & observation of features less code is reviewed.

Maybe soon just looking at outcomes. Things are moving quickly.

[dmix]

Sounds like a different use case than Cursor. Editing that many files/lines probably scales better with a CLI tool. Cursor makes more sense for day-to-day maintenance and heavy hand-holding feature development coding.

If I was building a new project from scratch I'd probably use a CLI tool to manage a longer TODO easier. But working on existing legacy code I find an IDE integration is more flexible.

[esafak]

And this unreviewed code is going into production?