šš„ Leaders Made the Monkeys. Now the Dragons Are Coming Back. And This Time, Age Is Not What You Think It Is
- Sarah Gruneisen
- 4 hours ago
- 5 min read
This conversation has come up three times in the last few days.
Thatās not coincidence.
Thatās a signal. š²
Because something deeper is happening in tech right now.
Experienced engineers are returning.
Younger engineers are pushing differently.
AI is accelerating everything.
And underneath it all?
š„ Weāre finally seeing the consequences of the systems we built.
š„ And how age shaped what each group had to learnā¦ and unlearn.
š Layer 1: The Uncomfortable Truth (Yes, This Includes Age)
We didnāt lose great engineers.
We trained them differently across generations.
Older engineers (often men, I was a rarity!) grew up in systems where:
š„ Thinking was expected, š¤ but not always shared
š„ Emotions were contained, š¤ not expressed
š„ Ownership existed, š¤ but came with pressure, not support
Younger engineers grew up in systems where:
š Expression is encouraged
š Boundaries are named
š Inclusion is visible
But even thereā¦
š¤ Ownership is often still restricted
š¤ Decision power still sits elsewhere
So what happened?
š²
We didnāt create ābetterā or āworseā engineers.
We created different survival strategies.
Older engineers often learned:
keep going, contain it, solve it, carry it.
Younger engineers often learned:
name it, question it, challenge it, protect yourself.
Both learned something real.
Neither learned the whole thing.
š And Then Leadership Broke the Bridge
Instead of integrating those differencesā¦
We built systems that:
š¤ Took decision-making away from both
š¤ Rewarded execution over thinking
š¤ Created approval layers that signal, āyouāre not trusted anywayā
So both groups adapted.
š¤ Older engineers disengaged or left
š¤ Younger engineers never fully learned ownership
And then we said:
āWhy are people passive?ā
š²
Because we built systems that train passivity.
We trained people to deliver without deciding.
To execute without modelling.
To comply without questioning.
And now with AI?
We are in danger of scaling that exact pattern.
š Thatās Why They Left, Why I Left ;-) (And Why Age Matters Here)
Many experienced engineers didnāt just leave randomly.
They reached the edge of what the system allowed them to be.
They saw:
š¤ The gap between responsibility and authority
š¤ The cost of misalignment
š¤ The human side of broken systems
š¤ The emptiness of being measured only on output
So they moved into:
š„ Leadership
š„ Coaching
š„ System thinking
Not because they aged out of engineeringā¦
š²
But because they outgrew the narrow definition of it.
They were no longer interested in only shipping code.
They wanted to understand:
Why are we building this?
Who decided this?
What breaks if we get it wrong?
Why do smart people keep ending up in dumb systems?
That is not āless technical.ā
That is deeper technical maturity.
š And Nowā¦ Theyāre Coming Back (Differently)
And now theyāre coming back.
But not as āolder engineers.ā
Not as people trying to rewind time.
Not as nostalgic coders wanting one more ride.
Theyāre coming back as something more valuable than that:
š Engineers who understand consequences.
š Engineers who understand systems beyond syntax.
š Engineers who have seen what happens when humans, incentives, architecture, and power drift apart.
That is why they are more needed now than ever.
Because we are entering a phase where:
š„ Building is getting cheaper
š¤ But wrong decisions are getting more expensive
AI can generate code.
AI can accelerate delivery.
AI can help ship faster.
But AI does not carry lived consequences.
It does not remember the re-org that killed accountability.
It does not feel the six months lost to misalignment.
It does not notice the team quietly stopping to think because leadership made thinking unsafe.
These returning engineers do.
And that changes everything.
š Why They Are More Needed Than Ever
This is the part that needs to land hardest.
They are more needed now because the bottleneck has changed.
It is no longer mainly:
Can we build this?
It is now:
Should we build this?
What will this break later?
Where is ownership eroding?
Which trade-off are we making without naming it?
Are we scaling intelligenceā¦ or scaling monkeys?
That is why pure coding is not enough.
That is why pure coaching is not enough.
We now need people who can hold:
š technical depth
š system awareness
š human dynamics
š long-term consequence
The engineers who stepped into leadership, coaching, and strategy learned exactly that.
They learned where teams fracture.
They learned how misalignment silently kills momentum.
They learned that bad architecture hurts, but broken ownership hurts more.
They learned that psychological safety is not a fluffy extra, it directly shapes quality, risk, and decision-making.
So when they come back, they do not just contribute output.
š²
They restore thinking.
š The Age Nuance We Keep Missing
This is not really about age as a number.
It is about what different eras trained people to become.
Older engineers often bring:
š Pattern recognition
š Calm under pressure
š Trade-off maturity
š Emotional regulation without always having the language for it
Younger engineers often bring:
š Emotional language
š Stronger boundary awareness
š More visible inclusion instincts
š Courage to question toxic or outdated norms
And again, both matter.
Because:
Expression without regulation can collapse under pressure
Regulation without expression can become silence
One names the tension.
One can often hold the tension.
The rare power is in the marriage of both.
That is where leadership lives now.
š Leaders Made the Monkeys
So letās say the sharp part clearly.
If developers stop thinking, that did not start with AI.
If engineers defer too quickly, that did not start with youth.
If ownership is thin, that did not start with individuals.
š²
Leaders made the monkeys.
Leaders built systems where curiosity was inconvenient.
Where approvals outranked proximity to the work.
Where engineers were close enough to carry responsibility, but not close enough to carry real authority.
Then we layered AI on top!
And now everyone is panicking that people are relying too much on the tool.
No.
The tool is just amplifying what the system already trained.
AI will not create ownership where leadership removed it.
It will not create judgment where systems punished judgment.
It will not create courage where people learned that thinking for themselves gets overruled anyway.
That is why the dragons are coming back.
Not just to code.
To interrupt the madness.
š The Leadership We Need Now
So what does leadership need to do now?
Not romanticize age.
Not dismiss youth.
Not split technical and human intelligence into different boxes.
But integrate.
ā¤ļøāš„ Pair younger engineersā emotional awareness with seasoned engineersā long-horizon judgment
ā¤ļøāš„ Give decision-making back to the edges
ā¤ļøāš„ Reward modeling, not just motion
ā¤ļøāš„ Stop treating expression and regulation as competing virtues
ā¤ļøāš„ Design teams where complementarity matters more than sameness
Because the future does not belong to the loudest, youngest, oldest, fastest, or most polished.
It belongs to the teams that can bring together:
š„ fire and restraint
š expression and steadiness
š curiosity and consequence
š youth and experience
Final Reflection
They didnāt leave because they were done.
They left because the system had become too small for what they could see.
And now theyāre coming backā¦
not older,
not outdated,
not confused.
š²
More complete.
So maybe the real question is not:
āWhy are they returning?ā
But:
āAre we finally ready to build engineering cultures where thinking, feeling, ownership, and experience were never meant to be separated?ā
The dragons are coming back. How exciting. As time goes on we should see better synergy between the younger and the wiser as we adapt to the new realities.