Engineering leadership is not tested when everything is calm.
It is tested when production is down.
When the deadline moves.
When executives start pacing.
When the customer escalates.
When the codebase fights back.
When the team loses confidence.
When someone has to make the hard call.
That is when leadership needs more than process.
More than charisma.
More than a framework.
More than a dashboard full of metrics.
Leadership under pressure needs virtues.
Not virtues as inspirational wallpaper.
Not “be honorable” fluff.
Virtues as practiced behavior when the situation gets expensive.
The Romans had a language for this:
-
Virtus
-
Gravitas
-
Pietas
-
Disciplina
-
Constantia
I am not interested in cosplaying Rome.
I am interested in the fact that people under pressure have not changed much.
Software is new.
Human behavior is not.
Teams still panic.
Leaders still avoid hard decisions.
Organizations still reward motion over judgment.
Smart people still chase preference over discipline.
Good intentions still create damage when duty is misordered.
Old virtues still have work to do.
Gravitas: Do Not Amplify Panic
A leader’s emotional state becomes team weather.
That matters.
When production is down, the team already knows it is serious.
When a customer escalates, the team already feels the pressure.
When an executive gets anxious, that anxiety travels quickly.
The engineering leader’s job is not to make the room feel the stakes.
The job is to create enough calm to let the team think clearly and move well.
Gravitas does not mean pretending nothing is wrong.
Gravitas means refusing to make the situation harder by adding panic to it.
Panic is rooted in fear.
Frank Herbert wrote, “Fear is the mind-killer.”
That line belongs in every production outage.
I have been through many large production outages.
I have even caused one.
Proper diagnosis and remediation require complete clarity of thinking.
The bigger the stakes, the clearer and colder your thinking has to be.
Think slow.
Move slow.
Communicate frequently and clearly.
Do not panic.
Name the problem.
Clarify the next step.
Assign ownership.
Protect attention.
Do not flood the team with emotional noise and call it leadership.
The person in charge does not get to be the loudest source of instability in the room.
Disciplina: Standards Beat Preference
Disciplina is not punishment.
It is ordered practice.
Software teams need it badly.
A healthy codebase cannot depend on every engineer carrying a private version of “good.”
One person likes factories.
Another likes orchestrators.
Another wants a new language.
Another wants to refactor the UI stack.
Another wants to introduce the pattern they read about last weekend.
That is not architecture.
That is preference sprawl.
Disciplina is putting standards ahead of preferences.
The team needs shared rules.
Shared conventions.
Shared patterns.
Shared definitions of done.
Shared expectations for how work moves through the system.
This is not bureaucracy.
It is how you protect cognitive load.
It is also how you make AI-assisted development safer.
Agents can follow explicit conventions.
They cannot reliably infer tribal knowledge scattered across five conflicting patterns.
Disciplina is what turns taste into a system.
Constantia: Principles Under Pressure
Principles are easy when nothing is at stake.
Everyone believes in clear requirements until the deadline is tight.
Everyone believes in code review until the release is late.
Everyone believes in standards until the exception is convenient.
Everyone believes in protecting the team until an executive asks for “just one quick thing.”
Constantia is consistency under pressure.
It is the discipline to remain the same kind of leader when the room gets tense.
Not rigid.
Not stubborn.
Not blind to reality.
Consistent.
Do you live your principles, or are they lip service?
That is the test.
If your principles disappear when the deadline gets tight, they were not principles.
They were preferences.
The team learns the difference quickly.
They watch what gets sacrificed first.
They watch which standards are real.
They watch whether leadership means what it says when saying it becomes expensive.
AI makes this even clearer.
If human developers have to work from clear stories, the AI has to work from clear stories.
Same format.
Same standards.
Same process.
You do not get to claim you value disciplined delivery, then let an agent bypass the discipline because it feels faster.
Constantia is how trust compounds.
Pietas: Duty Correctly Ordered
Pietas is usually translated as duty.
That translation is too thin, but it is close enough to start.
For a manager, duty never runs in one direction.
You owe something to the individual.
You owe something to the team.
You owe something to the business.
You owe something to the customers.
You owe something to the craft.
Sometimes those duties conflict.
That is where management becomes serious.
Duty is not severity.
Duty is protection correctly ordered.
You protect the person where you can.
You protect the team when you must.
You protect the business from avoidable damage.
You protect customers from instability.
You protect future maintainers from today’s cowardice.
Compassion matters.
But compassion without boundaries becomes negligence.
A manager who avoids a hard decision because it feels unkind is simply transferring the pain to everyone else.
That is not kindness.
That is misordered duty.
Virtus: Courage As Managerial Action
Virtus was a foundational Roman concept tied to martial courage, manliness, excellence, and character.
Manliness does not map cleanly to modern engineering leadership.
Martial courage needs translation.
Not violence.
Not conquest.
Action under pressure when stakes, risk, and fear are real.
In that sense, it maps very well.
The useful parts are courage, excellence, and character.
Courage belongs under character.
Not courage as personality.
Not courage as a strong opinion in a meeting.
Not courage as performative bluntness.
The Latin word root for heart is cor. It gives us courage. Virtus gives us virtue:
-
Upholding high standards
-
Holding principles when pressure rises
-
Doing the right thing when other demands make the wrong thing easier to justify
This is the most emotional of the virtues.
Because courage is not needed when doing the right thing is painless.
It is needed when doing the right thing can cost you something.
Courage is doing the right thing even when you are scared.
Courage is making the necessary call when avoidance would be easier.
It is doing or advocating for the right thing when the room wants something easier.
Sometimes that means putting features ahead of the tech debt remediation the team wants.
Sometimes it means putting tech debt remediation ahead of the features the business wants.
The direction is not the point.
The truth is.
Kill the bad project.
Escalate the real risk.
Tell the executive the plan is not credible.
Speak truth to the C-suite.
Give the direct feedback.
Remove the person harming the team.
Stop the rewrite that has become an ego project.
Say no to the shiny technology that only one person can maintain.
Protect the team from chaos even when the chaos comes from someone with more authority than you.
These moments do not feel noble while you are in them.
They feel heavy.
Your stomach tightens.
You wonder if you are about to damage a relationship, lose political capital, disappoint the team, anger the business, or make the wrong call in public.
That is why it is courage.
Not because you are certain.
Because the decision matters and you act anyway.
That is virtus in engineering leadership.
Not vibes.
Action.
Old Virtues, Modern Pressure
The point of this post is not that Latin is magic.
It is not.
The point is that engineering leadership keeps running into ancient human problems.
Fear.
Pride.
Avoidance.
Appetite.
Cowardice.
Status.
Panic.
Misordered loyalty.
Software changes quickly.
Pressure does not.
That is why these old words are useful.
They give us a way to name the behaviors leaders need when things get difficult.
Gravitas: stay steady.
Disciplina: keep standards.
Constantia: remain consistent.
Pietas: order your duties correctly.
Virtus: act with courage.
Not because ancient Rome had all the answers.
Because leadership still fails in familiar ways.
And when it does, teams do not need slogans.
They need leaders with practiced virtues.