Orestis Ioannou uses coding agents throughout his engineering work. They made previously impractical projects worth starting, but each parallel task eventually returns with questions or code to review. His capacity to implement has outgrown his capacity to think through everything he starts.
- His GitHub history shows 2,102 contributions through October 27, approaching the 2,371 recorded over the same period in 2020.
- He now leads engineering at Bold.org. His activity is back near his full-time feature-development pace, despite having fewer feature responsibilities.
- He describes three cycles of starting more work after a new model or workflow, then pulling back as reviewing and context switching become exhausting.
Caveat: contributions mix commits, reviews, issues and pull requests; this personal history cannot establish hours worked, value delivered or AI’s causal effect.
The 514-comment thread on Hacker News adds concrete boundaries and competing experiences to an essay whose author says he has yet to find a balance.
What the thread adds
- ak39 — a daily stopping rule: “Make a finite list for the day, tick it off and go spend time with the missus, the kids or the dog.”
- carlgreene — a boundary on always-available agents: “I switched to a dumb flip phone as my primary device and now my work mostly only gets done on my computer during work hours.”
- thatguymike — a proposed explanation for fatigue: “the boring parts were also protecting us.” They describe the remaining work as demanding constant attention.
- clord — a counterexample to the gloomy reading: “I notice I am doing more work as well but enjoying it and taking more time to recharge.”
- Pingk — a collective remedy rather than another workflow adjustment: “Join a union and campaign for a 4-day work week or something.”
HN handles are pseudonymous, and no per-comment scores are public; the sample follows HN’s ranking and is a slice of the thread, not a consensus.