The Art of Delegating: Orchestrating Jules and Claude in Everyday Life

There’s something deeply strange and yet familiar about watching two artificial intelligence agents—Jules and Claude—collaborate on a codebase while my youngest daughter sleeps in the next room. As a software engineer, automation has always been the holy grail; As a parent, delegation has become a necessity for survival. But the intersection of these two realities revealed an unexpected complexity: that the real difficulty is not in making machines work, but in knowing how to supervise them without suffocating them. In my day-to-day ontology, each task I delegate to Jules (generally focused on engineering tasks and rigorous scaffolding) or to Claude (more prone to synthesis and lateral thinking) is not a mere command executed in a vacuum. They are events. And, as a process philosopher would argue, they are events all the way. Each prompt is a disturbance in the system, a coded intention that reverberates through latent space until returned as code, text, or architecture.

The Paradox of Control#

The hardest lesson I learned in the last year orchestrating these agents came not from a syntax error or an infinite loop, but from my own psychology. The engineer’s initial impulse is micromanagement. We want to review each line of code as it is generated, correct each comma, guide the invisible hand of the machine. However, I’ve found that treating autonomous agents as mere extended keyboards undermines the very advantage they provide. It’s like trying to teach a child to walk by holding their heels. The magic happens when you define the contours of the problem, the success criteria (the “schema”, if you prefer), and allow the agent to navigate the solution space. But how to maintain human supervision? How to avoid the silent hallucination that corrupts an entire system?

The Practice of Architectural Supervision#

The answer I found lies in a change of posture: I stopped being the executor to become the architect and the editor. When I entrust Jules with refactoring a microservice, I don’t look at the code while he writes it. I build rigorous tests and CI/CD pipelines that act like the laws of physics of that particular universe. Human oversight is transmuted into systemic constraints. If Jules’ code compiles and passes the integration tests I designed, he has the freedom to be idiosyncratic in his implementation. Claude, on the other hand, serves as my system design and philosophical reflection partner. When we discuss the intelligibility of a new architecture, my oversight is rhetorical. I apply Socratic skepticism, forcing the model to justify its structural choices against the practical constraints of business and long-term maintenance.

Paternity and Process#

There is an undeniable parallel between managing these agents and raising children. In both cases, you are dealing with entities that possess a degree of autonomy, that interpret your instructions in unpredictable ways, and whose “output” does not always correspond to their original intent. When my daughter builds a tower of blocks and it collapses, my role is not to rebuild it perfectly. It’s helping her understand gravity. Likewise, when an agent proposes an overly complex design pattern, my role is to redirect their attention to first principles.

Events Until the End#

Ultimately, orchestrating AI is an exercise in epistemic humility. It is accepting that we cannot (and should not) have absolute control over every atomic operation of our systems. We must focus on boundary conditions, interfaces and fundamental guarantees of stability. Effective delegation to AI is not the abdication of human responsibility. It is your elevation to a higher order of abstraction. As I watch the terminal run the test suites written by Jules, and Claude’s text take shape on the screen, I realize that we are not building tools that replace us. We are building a new kind of collaborative system, where human judgment and machine probabilistic brute force converge in a complex, ongoing dance. The screen glows in the dark office. The baby breathes gently through the baby monitor. And events continue to unfold.