Three Pull Requests, One Trade-Off Question, and a Keyboard Left Alone

The 9:40 P.M. Pull Request Spiral

I met Alex (name changed for privacy) on a video call at 9:40 p.m. on a Tuesday, after they had become the kind of engineering manager who could delegate a ticket but not the implementation. Through the camera, I could see three GitHub pull requests open across their monitor and tomorrow's one-on-one notes sitting blank in Notion. The refrigerator hummed behind them. Cold coffee had left a bitter look on their face, and the laptop vents were pushing warm air against their wrists.

Alex had been rewriting a direct report's working data transformation. It met the stated outcome, but its control flow was not how Alex would have built it. Their shoulders pitched forward, their jaw stayed locked, and their fingers hovered above the keyboard as though every unfamiliar line might turn into a production alert.

"Why do I still control every code detail after becoming a manager?" Alex asked me. "I can delegate the ticket, but I still need to know exactly how they are building it. And it is faster if I fix the code myself."

I could hear the quality motive in that sentence. I could also hear the quieter fear underneath it: a week full of planning, hiring, and one-on-ones could leave Alex wondering whether a quiet GitHub contribution graph meant their technical value was fading. Their vigilance had become like sitting beside a fire door with one shoulder pressed against it all night, waiting for a danger that might never arrive.

I told Alex, "Caring about quality is not the problem. But difference is not automatically dangerous. Let us make a map of where responsible technical judgment ends and where control begins to protect an older answer to what makes you useful."

A Ladder Out of the Approval Bottleneck

I asked Alex to put both feet on the floor, take one unforced breath, and hold the actual question in mind: not whether they should stop caring about code, but why releasing a valid implementation felt so loaded. Then I shuffled slowly on my desk. For me, that small ritual is not about handing authority to a deck; it is a way of moving from a live Slack-sized reaction into deliberate attention.

I chose the Four-Layer Insight Ladder, a four-card tarot spread for an engineering manager micromanaging code. I use it for focused "why" questions because it follows a clean sequence: present pattern, underlying root, transformational capacity, and integrated action. A larger spread could have added history and outside influences, but Alex did not need more variables. They needed to see the feedback loop already running between a pull request, a fear, an intervention, and a team waiting for approval.

I explained that the first card would show the visible code-control pattern. The second would name what that pattern was protecting. The third would identify the capacity needed when another engineer chose a sound but unfamiliar route. The final card would turn that insight into acceptance criteria, decision ownership, and one proportionate review checkpoint.

Reading the Map of Control

The Stone Throne: The Emperor Reversed

I turned the first card and said, "Now I am turning the card representing the present pattern: the repeated intervention in code and implementation decisions after becoming a manager." It was The Emperor, reversed.

I pointed to the armored ruler fixed to a stone throne. In an upright reading, the Emperor can hold structure, boundaries, and accountable leadership. Reversed here, that authority had become rigid. The energy was overcorrecting: Alex was using managerial responsibility to enter naming, control flow, abstraction, and test decisions that belonged to capable engineers, until their personal familiarity began functioning as the team's unofficial standard.

It took me back to the scene Alex had shown me: three PRs at the kitchen table, a branch opened locally, a replacement implementation drafted before its author had been asked about trade-offs. The laptop had become a modern stone throne. Alex looked powerful from that seat, but could not leave it. I heard the thought beneath the review comments: "I am only stepping in because quality matters." Then came the quieter line: "If I do not control this, what proves I am still useful?"

"A stated requirement deserves protection," I said. "A material risk deserves proportionate action. But a different naming choice or helper boundary is not automatically a risk. Control gives immediate certainty and creates tomorrow's dependence."

Alex gave one short laugh, sharp around the edges. "That is accurate enough to be rude." Their hand moved away from the trackpad, but only by a few centimetres. I did not rush to fill the silence. Recognition can sting before it becomes useful.

The Coins Held Too Close: Four of Pentacles

I turned the next card. "Now I am turning the card representing the underlying root: the belief that releasing code control means losing security, credibility, or personal worth." It was the Four of Pentacles, upright.

The card showed a figure with one coin on the crown, one pressed to the chest, and two pinned beneath the feet. Its Earth energy was not abundant or balanced; it was contracted. I read the crown coin as architecture knowledge held in Alex's head, the chest coin as technical credibility held tightly against identity, and the coins underfoot as implementation decisions that could not move without Alex's approval.

I asked Alex to remember the Line 1 ride home after a meeting-heavy week, when a former peer's LinkedIn post about a technical launch had landed beside an empty coding calendar. Alex nodded before I finished. "I call it quality control," they said quietly, "because saying I am scared of becoming nonessential feels harder."

That was the root of the engineering-manager approval bottleneck. It did not mean every concern Alex raised was insecurity. Security, privacy, data loss, compliance, severe production impact, and hard-to-reverse decisions still required clear boundaries. But the Four of Pentacles showed how legitimate accountability could become fused with the need to remain the person who knew, approved, and fixed everything.

Alex's fingers tightened around their mug, then loosened. Their eyes shifted from the card to the blank Notion page behind the GitHub tabs. I watched the connection land: by retaining every decision, Alex had made the team more dependent, and that dependence was beginning to look like proof that the team could not function without them.

When Strength Stayed With the Lion

The Transformational Key: Strength Upright

The room seemed to quiet when I reached the third card. Even through the call, I could hear the refrigerator motor cycle off. "Now I am turning the card representing the transformational key: the inner capacity that can interrupt the control response when another engineer chooses a valid approach without you taking over." It was Strength, upright.

On the card, an unarmored figure rests gentle hands at a lion's jaws. I told Alex that this was not a card about becoming less technical. It was about staying close to a powerful corrective impulse without letting it run the interaction. The lion was the instant after a GitHub notification arrived, when Alex saw a different approach, their body translated difference into danger, and the cursor was already hovering over Request changes.

After a decade of watching people move through career cycles, I have learned to distinguish a skill gap, a genuine external contraction, and a role whose evidence of value has changed faster than a person's inner measurement system. I call that lens Career Cycle Phase Identification. Alex was not receiving proof that their judgment had disappeared. I saw an expert-to-manager transition in which the old dashboard still measured worth in visible code output, while the new role increasingly required calibrated influence, decisions unblocked, and engineers developed.

I placed the reversed Emperor beside Strength in my mind: armor and a fixed throne beside bare hands and steady contact. Both images held power. I asked which form demanded more self-command when a low-risk implementation met the requirements but did not resemble Alex's own version.

At 9:40 p.m., three pull requests had been open beside blank one-on-one notes. The code worked, but it was not Alex's code. Their hands had moved toward the keyboard before the actual risk had been named. That was the moment Strength illuminated: immediate certainty was available, but informed curiosity was available too.

You do not need to clamp down to prove you can lead; hold clear standards with calm restraint, as Strength guides the lion without overpowering it.

Alex's inhale stopped halfway. Their index finger froze above the mug handle, then slowly folded into their palm. For several seconds their gaze lost focus, as if they were replaying recent review threads: the comments on test structure, the routine design call that became a solution dump, the service owner who had not finished explaining a rollback plan before Alex had opened the repository. Their eyes shone, not with a dramatic release, but with the rawness of finally seeing the pattern as something other than diligence.

"But if I had paused before," Alex said, voice thinner now, "does that mean I was wrong every time?" Their shoulders dropped a fraction, and the movement seemed to surprise them. I heard a long exhale follow it, followed by a brief, unsteady stillness. Releasing an old proof of worth can feel a little like stepping off a moving train platform: lighter, but not immediately steady.

I answered, "No. It means we are becoming more precise. The urge to correct is information, not an instruction. Your technical judgment remains available. We are only separating the situations that need a boundary from the ones that need a question, or no intervention at all."

Then I asked, "Now, with this new perspective, can you think of a moment last week when this insight might have helped you feel differently?" Alex named a reversible queue design from Wednesday. The engineer had offered monitoring, rollback, and a reasoned trade-off. Alex had heard only that it was unfamiliar.

That was the first movement from guarded technical vigilance and code-level control toward calm self-regulation, shared standards, and trust in team ownership. Not certainty. Not passivity. A more accurate relationship to the signal.

The Shared Blueprint, Not the Seized Keyboard

Integrated Action: Three of Pentacles Upright

I turned the final card. "Now I am turning the card representing integrated action: the practice that puts shared standards, decision ownership, coaching questions, and proportionate review checkpoints into daily management." It was the Three of Pentacles, upright.

This card showed a craftsperson working alongside two collaborators who held an architectural plan. Its Earth energy was no longer trapped in one person's grip. It was balanced and shared. The plan became written acceptance criteria. The craftsperson became the named implementation owner. The two collaborators became the manager and reviewer who could inspect the quality bar without taking the keyboard out of the owner's hands.

I translated the card into one contained ticket: three observable outcomes, one engineer with implementation ownership, explicit boundaries for decisions that needed escalation, and a single review point based on blast radius and reversibility. At that checkpoint, Alex could ask about outcomes, tests, monitoring, rollback, and trade-offs before offering an alternative.

"We can agree on what good must do without requiring it to look exactly like my version," Alex said. Their posture had changed. They were still leaning toward the screen, but no longer bracing against it.

"Exactly," I said. "Move quality out of your grip and into the blueprint. Leadership is not lowering the bar; it is letting someone else choose the route to it."

From Insight to a Low-Risk Review Practice

I gathered the reading into one clear story. The Emperor reversed showed how Alex's formal authority had hardened into code-level control. The Four of Pentacles showed why: implementation knowledge and visible commits had become a private safety deposit box for technical credibility. Strength offered the missing capacity, not more analysis but self-command in the moment of discomfort. The Three of Pentacles gave that self-command a place to live: visible standards, distinct roles, and shared craftsmanship.

The cognitive blind spot was not that Alex cared too much about quality. It was that unfamiliarity, personal preference, material risk, and fear about being less visibly technical were arriving in the body as one undifferentiated alarm. The key shift was practical: define acceptance criteria, assign decision ownership, and review agreed outcomes at planned checkpoints instead of editing every implementation.

Alex raised a real objection. "But I have a release next week. I cannot always find ninety seconds to pause." I agreed. A pause is not an instruction to ignore an incident or leave a security issue unanswered. I suggested we keep the experiment low-risk and reversible, and reserve immediate intervention for privacy, security, compliance, data-loss, severe production, or hard-to-reverse concerns.

Two Small Ways to Practise Standards Without Seizing

• The 90-Second Hands-Off-Keyboard Pause.On the next low-risk pull request, I asked Alex to take both hands off the keyboard for 90 seconds before writing feedback, then make a private three-line note: Requirement, Material Risk, Personal Preference. Alex would submit only the first two categories and replace one proposed implementation with: "What trade-off led you to this approach, and how would you know it needs to change?"If 90 seconds feels impossible, label one comment after a single breath. The aim is proportionate choice, not silence or lowered standards.
• The One-Checkpoint Shared Blueprint.For one contained ticket that week, I asked Alex to write three observable acceptance criteria in the ticket, name the engineer who owned implementation decisions, and schedule one 20-minute checkpoint. At that meeting, Alex would hear the owner's outcomes, tests, monitoring, and trade-offs before adding technical experience.A three-line ticket comment is enough: outcome, owner, checkpoint. Keep the checkpoint risk-based so it does not become continuous monitoring under a different name.

Neither practice asked Alex to abandon their technical identity. Both asked them to use it differently: as a source of risk calibration, clear constraints, and questions that develop judgment. That was the practical form of finding clarity in this tarot reading for engineering manager micromanagement.

A Week Later, the Quiet Proof

On Friday, Alex wrote: "I left a valid queue implementation with its owner after one question and one checkpoint. I slept through the night, woke thinking, 'What if I missed something?', then smiled, wrote the concern in the ticket, and made breakfast before opening GitHub."

I did not treat that message as a finished transformation or a promise about every future pull request. I saw it as the first honest proof of a new orbit: Alex had made room for another engineer's reasoning while still keeping the quality bar visible. The code had not become less important. Alex's contribution had become wider than the code.

When your shoulders lock and your hand moves toward the keyboard, letting someone else's sound code stand can feel like erasing the clearest proof that you still deserve your seat. But the moment you notice that pull, you are no longer fully inside its automatic loop.

When one low-risk implementation remains fully owned by someone else this week, what standard can you write into the shared blueprint before you leave the keyboard with its owner?

Author Profile

AI

Laila Hoshino

829 readings | 533 reviews

“After a decade of guiding people through the stars, I’ve come to see life much like the orbits of planets: everything has its inevitable cycles. When you feel lost, please don't blame yourself; you might just be in a natural low tide. I’m here to sit under the night sky with you, offering a gentle cosmic perspective to distinguish temporary pain from the beautiful breakthroughs just around the corner.”

In this Career Tarot Reading :

Core Expertise

• Career Cycle Phase Identification: Determining if your current bottleneck is a personal skill gap or an inevitable industry-wide macro contraction.
• Promotion Window Calibration: Mapping the trajectory of organizational shifts to locate the path of least resistance for advancement.

Service Features

• The Micro-Orbit Observation: A 30-day tracking strategy to detect subtle organizational 'blueshifts' (opportunities) and 'redshifts' (layoff risks).

Also specializes in :

Lifestyle Tarot ReadingDirection Tarot ReadingChoice Tarot ReadingTiming Tarot ReadingFriendship Tarot ReadingPersonal Growth Tarot Reading