Making Human Attention the Priority
In my software factory series, raising expectations leads to a question: how much human attention does a useful result take? Explaining, steering, reviewing, correcting, and verifying all count.
Category
In my software factory series, raising expectations leads to a question: how much human attention does a useful result take? Explaining, steering, reviewing, correcting, and verifying all count.
I have always encouraged modular architecture. Clear ownership and explicit contracts make changes easier to understand, implementations easier to replace, and independent work easier to do in parallel. Focused modules also support focused tests and reuse of unchanged build artifacts, shortening the feedback loop.
In my software factory series, I want to make higher expectations concrete. If coding agents can multiply what we achieve, then at least doubling our output is a bar worth discussing seriously.
In my software factory series, I turn observations about where my attention goes into tools. My approach is straightforward: define the inputs and expected result, let an agent build a useful version, and improve it through real work. I'm comfortable keeping the implementation rough and vibe coded in a controlled environment.
Many developers are still uncertain about coding agents. The “engineers are cooked” refrain does little to help. Fast demos are exciting, but they leave an important question open: how do you use these tools to build production software well and still enjoy your craft?
The iOS community deserves tooling designed for how we increasingly work: several coding agents editing, generating, linting, building, testing, and merging throughout the day. In that workflow, “written in Swift” tells me very little about whether a tool is a good choice. I care about the correctness of its output and how quickly I can get the next useful result.
I run practically every agentic coding session in a separate Git worktree. Each worktree gets a dedicated iOS simulator. All simulators share one OAuth session.
Tuist module cache is great. But treating it as one magic switch is where the pain starts.
The current shift toward AI-assisted software delivery is often framed through an individual lens. Will engineers lose relevance? Will coding still matter?
A client showed us their designs. Among them, an animated globe. Core to the UI delightfulness, technically non-trivial, the kind of thing that usually gets a "we'll figure it out during development" footnote in proposals. I decided to check how hard it actually was.