theJugglingCompany.com

Blog · 1 June 2026 · 7 min read TechChange

The Devil Stick Runs While You Work

In one hand: balls. Your active work, your code, your decisions. In the other: a devil stick. The managed service, the automated pipeline, the agent crew - spinning on its own, needing only occasional correction. This is the modern knowledge worker's actual pattern.

An upturned hand holding a glowing ball at its center, from which rise branches of juggling props - clubs, rings, balls - blooming into cloud icons and AI symbols

There is a juggling pattern that most people do not recognize as juggling.

One hand holds a devil stick - a thin baton that spins horizontally, propelled and guided by two small hand sticks. You hit it left, it spins right. You hit it right, it spins left. At steady spin, it almost manages itself. You do not need to touch it constantly. You tap it, correct its angle when it starts to drift, and let it continue.

The other hand is running a normal three-ball cascade. Throw, catch, throw, catch. Active work. Each ball requires attention and timing. The balls do not continue without you. They fall the moment you stop.

Two hands. Two completely different relationships to continuity.

Devil stick
Runs without you
Needs a tap to correct drift, but continues spinning between touches - managed services, automated pipelines, agent crews
Balls
Stops without you
Active work that requires continuous attention - your code, your decisions, your creative output
Both hands
The modern pattern
The skill is maintaining both simultaneously - knowing when to tap the stick and when to trust the spin

What the devil stick is

The devil stick does not require constant contact. Once you have set it spinning at the right speed and angle, it will continue for a while without your intervention. But it will drift. The angle will tilt. The spin will slow. If you wait too long to correct it, the spin dies and you have to restart from zero, which is harder than maintaining the spin that was already there.

The skill of devil sticking is not in the continuous contact. It is in reading the spin, knowing when it needs correction, and making that correction small and precise rather than large and compensatory. A well-timed small tap keeps the spin clean. A late large correction often makes it worse.

This is an exact description of how managed cloud services work.

An AWS Lambda function, a fully managed database, a containerized API on App Runner, an AI agent crew running on a schedule - these continue operating when you are not touching them. They do not need you to watch them every second. They run. But they will drift: configurations that worked in one context become misaligned in another, costs that were predictable start growing in unexpected directions, models that were well-calibrated start encountering data patterns they were not trained on.

The skill is not in constant monitoring. It is in reading the spin - watching the right signals - and correcting early while the correction is still small.

LEFT HAND - Active WorkRIGHT HAND - Managed Servicescontinuous throw-catch-throw cyclestops the moment you stopspinning - autonomoustapcorrectperiodic small correctionscontinues without you between touchesbut drifts without them
Two-handed pattern: active work in one hand requires continuous attention, managed services in the other need periodic correction not constant contact

The balls in the left hand

The three-ball cascade running in the left hand is your active work. The code you are writing. The architecture decisions you are making. The conversations you are having. The creative and strategic work that requires your continuous attention and does not continue when you look away.

This work does not benefit from autonomy. It benefits from your presence - your judgment, your experience, your ability to read what is happening and respond in real time. The balls fall the moment you stop throwing.

The relationship to these balls should not be automation. It should be depth. The left hand runs the active pattern because that is what it is for.

Reading the spin: what good monitoring looks like

The most common failure in the two-handed pattern is neglecting the devil stick because the balls are demanding.

The cascade in the left hand requires constant rhythm. The devil stick, because it does not fall immediately, is easy to deprioritize. You stop watching it. The spin slows. The angle tilts. By the time you notice, the correction is not a small tap - it is a full restart.

In cloud infrastructure, this is the pattern behind most incidents involving managed services. The Lambda function was running fine for months. The costs drifted. The database connections quietly saturated. The agent’s outputs started degrading as the model encountered new patterns. None of these required immediate intervention at the moment they began. All of them required a small correction before they became large corrections.

You do not monitor the devil stick by watching it every second. You monitor it by knowing what a healthy spin looks like, checking that what you see matches it, and correcting when it does not. The check takes a moment. The correction, when done early, takes a moment more. Neither interrupts the cascade.

The combination is the skill

Running balls in one hand is a skill. Running a devil stick in the other hand is a skill. Running both simultaneously is a third skill that is not simply the sum of the two.

The combination requires a different kind of attention management. The balls demand rhythmic presence. The devil stick demands periodic peripheral awareness. Neither can receive all of your attention at once. Neither can be fully ignored.

The image for this post shows a hand holding a glowing ball at its center, with branches growing upward - props, rings, clubs blooming into cloud icons and AI symbols. The ball in the hand is the active foundation. Everything branching outward is the autonomous layer that grew from it. The hand still holds the original ball. The branches run on their own.

That is the pattern. Start with what you hold. Let what can run autonomously run. Keep your hands in both.


Read next: The Change Is Always Juggling - the structural pattern that runs through every major organisational change.