Of my friends who use coding agents heavily, the happiest seem to fall into two distant camps:
a) Controlled fast loops: 1-2min cycles, mostly single-threaded, still totally in control of the code, using the agent "to type faster"
b) Delegated slow loops: Nudging along in the background a couple times a day, while something else (design, writing, etc) is their primary focus; paying ~no attention to code; it's fine if agents get stuck for hours
Like many, I've been trying to make some middle ground work: trying to delegate more than the first camp, while giving the work more focus and technical oversight than the second. My role is planning, technical guidance, and code review. This leads to 10-30min cycles, which lead to parallelism (to avoid busy-waiting), which leads to context-switching and fragmentation, which leads to working memory churn and poor comprehension, which leads to situations where neither the agents nor I understand what's going on.
It sucks and I hate it. I'm moving faster, but the work is unpleasant and unrewarding. It seems awfully hard to exert *partial* technical control—much easier to exert ~full or ~none.
The ideal, maybe, is something like what @simonlast outlines in https://t.co/M6R3EF5Yy7: teams of agents making technical plans, reviewing each others' work, autonomously and adversarially testing, etc. You still get robust "technical oversight"—just by other agents. Unfortunately in my domain (mobile interface with heavy gestures and animation) that's not yet tractable, even with lots of homegrown scaffolds and probes. But things will probably look very different in a year.
I'm curious if others have found happy middle ground between these poles?
Xcode 27 is the first version that ships Agent Skills. I looked closer into its SwiftUI one and found great learnings, but also room for improvement.
https://t.co/K5cYsp3J9C
#swiftlang#iosdev
📚 Booklover v3.7.1 is out. Editing selected books now preserves the selection, letting you jump straight into another action. This update also fixes rendering issues on full-screen PDF pages with scaled-down images, along with other minor improvements.
This issue seemed resolved in iPadOS 26.1, but it looks like it resurfaced in 26.3. Since there is currently no known fix on the app side, please use the workaround mentioned in our FAQ for now. (We expect a future OS update will likely fix it again.)
📚 Booklover v3.7.0 is out. (1) Genre sections in the Library can now be collapsed and expanded. Tap the chevron on the left of a genre header to collapse or expand that genre. You can also long-press the chevron to open a menu and collapse or expand all genre sections. (Cont.)