The 42 Principles · Principle XLII
Leave Something Better Behind
Purpose, legacy, gratitude, contribution, succession, and measuring life by what others can build because we were here.
The Answer
Forty-one Principles brought us here.
We have talked about engineering.
Systems.
Failure.
Security.
Complexity.
Truth.
Trust.
Ownership.
Knowledge.
Teaching.
Leadership.
Curiosity.
And people.
We have asked how to build.
How to troubleshoot.
How to decide.
How to recover.
How to lead.
How to learn.
How to teach.
How to become better at the work.
But there is a larger question.
What was all of it for?
My answer is simple.
Leave something better behind.
More Than the Work
Eventually every project ends.
Every system is replaced.
Every technology becomes old.
Every architecture becomes legacy.
Every company changes.
Every career ends.
If the only evidence that we were here is the technology we personally built, time will eventually erase most of it.
That sounds discouraging.
I don't think it is.
Because our work leaves behind more than artifacts.
It changes people.
It changes knowledge.
It changes expectations.
It changes what becomes possible next.
The system may disappear.
The effect does not necessarily disappear with it.
The First Thirty-Eight Principles Were Already Pointing Here
Build things that work.
Understand the problem before solving it.
Protect what matters.
Reduce unnecessary complexity.
Design for failure.
Automate toil.
Understand dependencies.
Measure what matters.
Tell the truth.
Admit what you don't know.
Own the outcome.
Earn trust.
Keep your word.
Teach.
Solve real problems.
Make things better than you found them.
None of those ideas exist only to create better technology.
They describe a way of taking responsibility for the small piece of the world temporarily placed in your hands.
That is the larger lesson.
The work was never only about the work. It was about what became better because you did it well.
Temporary Custodians
Almost nothing we work on truly belongs to us forever.
We inherit systems built by other people.
Networks.
Applications.
Databases.
Documentation.
Processes.
Organizations.
Knowledge.
Then, for a while, they become our responsibility.
We change them.
Repair them.
Extend them.
Protect them.
Sometimes replace them.
Eventually someone else inherits what we leave.
We are custodians.
Temporary ones.
That should change how we work.
Someone Comes After You
This idea appears throughout this book because I believe it deeply.
Someone comes after you.
Another engineer will read the code.
Another administrator will inherit the server.
Another technician will troubleshoot the network.
Another manager will lead the team.
Another person will read the documentation.
Another customer will use the product.
Another generation will inherit the institution.
You may never meet them.
Your decisions still affect them.
Good stewardship is respect for people you may never have the opportunity to meet.
Leave Them a Better Starting Point
You do not need to solve every future problem.
You cannot.
But you can improve where the next person begins.
Document what you learned.
Remove the unnecessary dependency.
Automate the repetitive task.
Fix the misleading name.
Explain the strange configuration.
Preserve the reason behind the decision.
Create the rollback procedure.
Teach someone else.
Clean up after yourself.
Fill the gas tank.
The next person should not have to rediscover everything you already paid to learn.
This Is Why Documentation Matters
Documentation appears repeatedly throughout these Principles because it is one of the simplest ways to communicate with the future.
You are saying:
I was here.
This is what I found.
This is what I changed.
This is why.
This is what you should know before touching it again.
Good documentation is an act of consideration for someone who is not in the room yet.
Sometimes that person is you six months later.
Sometimes it is someone you will never know.
Either way, leave the note.
This Is Why Teaching Matters
Knowledge that ends with you has limited reach.
Teach someone.
Now the knowledge travels.
They use it somewhere you never will.
They improve it.
They teach someone else.
Eventually an idea you shared may influence work you never see.
That is extraordinary.
You do not have to personally touch every system to improve it.
Sometimes you improve the person who will.
This Is Why Enablement Matters
Principle XL asked us to enable others to succeed.
Now we can see why it belongs so close to the end.
Your reach is finite.
You can solve only so many problems.
Build only so many systems.
Attend only so many meetings.
Help only so many customers directly.
But capable people multiply.
If you help someone become better...
And they help someone else...
Your contribution travels farther than your own hands ever could.
This Is Why Institutions Matter
Principle XXXIX asked us to build institutions, not merely projects.
Because projects end.
Capability can remain.
A good process remains.
A standard remains.
A culture remains.
Knowledge remains.
People remain.
An institution carries useful ideas beyond the people who originally created them.
That is how temporary work produces durable value.
This Is Why Integrity Matters
You will make decisions nobody sees.
Shortcuts nobody would discover.
Documentation nobody forces you to write.
Risks you could quietly ignore.
Problems you could leave for someone else.
Integrity determines what you do in those moments.
Leaving something better behind often depends on work for which nobody will ever applaud you.
Do it anyway.
The person who inherits the result may never know your name.
They will still experience your decisions.
This Is Why Humility Matters
You will not finish the work.
None of us will.
There will always be another improvement.
Another problem.
Another generation.
Another idea.
Humility allows us to contribute without believing the story ends with us.
We build on what others left.
Others will build on what we leave.
That is how progress works.
Inherit With Gratitude
Leaving something better behind also requires recognizing what was left for you.
Someone wrote the language.
Someone designed the protocol.
Someone built the operating system.
Someone documented the standard.
Someone discovered the algorithm.
Someone installed the cable.
Someone answered the question.
Someone taught you.
Someone gave you the opportunity.
Nobody builds alone.
Every expert stands on an enormous foundation of work performed by people they will never meet.
Remember that before becoming too impressed with yourself.
Improve Without Contempt
You will inherit bad systems.
Confusing systems.
Undocumented systems.
Fragile systems.
Systems built with decisions you would never make today.
Improve them.
But be careful about judging the people who came before you.
You rarely know all the constraints they faced.
The deadline.
The budget.
The technology available at the time.
The requirements.
The emergency.
The knowledge they had.
The organization around them.
You can improve the past without insulting it.
Respect what you inherited enough to understand it, and respect what comes next enough to improve it.
Progress Is a Relay
Very little meaningful progress is completed by one person.
Someone begins.
Someone improves.
Someone discovers a problem.
Someone solves part of it.
Someone teaches.
Someone challenges.
Someone builds the next version.
Then someone else continues.
We like stories about individual genius because they are easy to tell.
Reality is usually more collaborative.
Progress is a relay.
You carry something for a while.
Then you hand it forward.
The important question is:
What condition is it in when you pass it?
Your Name Does Not Need to Remain
There is a temptation to connect legacy with recognition.
Buildings with names.
Awards.
Titles.
Products.
Books.
Maybe those things matter.
But some of the most meaningful contributions will never carry the contributor's name.
A process that quietly prevents mistakes.
A lesson someone still remembers.
A script that saves hours every week.
A person whose career changed because someone believed in them.
A decision that prevented a failure nobody knows almost happened.
Invisible contributions still count.
Legacy is not whether people remember your name. It is whether something remained better because you were here.
Better Does Not Mean Perfect
This book has never asked for perfection.
Perfection is usually unavailable.
Sometimes impossible.
You will leave unfinished work.
Unanswered questions.
Technical debt.
Mistakes.
Things you wish you had done differently.
So will I.
The standard is not:
Did you perfect everything you touched?
The better question is:
Did you move it in the right direction?
Did you leave useful knowledge?
Did you reduce unnecessary harm?
Did you make the next step easier?
Did you care?
Small Improvements Count
Not every contribution needs to change the world.
Fix the documentation.
Teach the new employee.
Clean up the script.
Call the customer back.
Correct the misleading instruction.
Automate the annoying task.
Listen to someone.
Share the credit.
Ask the question.
Keep the promise.
Do the extra fifteen minutes.
Small acts compound.
A career is made from them.
So is a reputation.
So is a culture.
So, eventually, is a legacy.
The World Does Not Need Your Perfection
It needs your contribution.
Something useful.
Something honest.
Something thoughtful.
Something that helps.
You do not need to know everything.
You do not need to solve everything.
You do not need to be the smartest person in every room.
You need to take what you have learned and use it responsibly while it is yours to use.
Then pass something worthwhile forward.
The Answer Was Never 42
Douglas Adams gave us a wonderful joke.
The answer to the ultimate question of life, the universe, and everything:
But the joke contains another lesson.
An answer without understanding the question is not particularly useful.
That is why this book was never really about finding one universal answer.
It was about learning how to approach the questions.
With curiosity.
Humility.
Integrity.
Discipline.
Responsibility.
And care.
There is no single command that solves everything.
No architecture.
No methodology.
No career lesson.
No Principle.
Not even this one.
Solve for 42
To me, solving for 42 does not mean discovering the final answer.
It means accepting that we may never have one.
And working responsibly anyway.
Ask better questions.
Solve the problem in front of you.
Tell the truth about what you know.
Admit what you don't.
Protect what matters.
Learn from failure.
Share what you discover.
Help other people become capable.
Build things worth inheriting.
Then leave the next person a better starting point than the one you received.
That is enough.
More than enough.
One Life, Limited Time
Eventually the number of projects remaining becomes smaller than the number behind us.
The number of problems we will personally solve becomes finite.
The number of people we can directly teach becomes finite.
Time makes that decision for everyone.
That is why what we pass forward matters.
Knowledge extends beyond our time.
People extend beyond our reach.
Institutions extend beyond our tenure.
Ideas extend beyond our presence.
We cannot stay.
But something we contributed can.
Closing Thought
You will not solve every problem.
You will not answer every question.
You will not finish everything worth building.
Neither will I.
That was never the assignment.
Take responsibility for what reaches your hands.
Learn everything you reasonably can from it.
Do the work well.
Tell the truth.
Help people.
Teach what you know.
Remain curious.
And when it is time to hand the work to someone else...
Leave them something better than you received.
You do not need to leave the world knowing your name. Leave it with something worth having because you were here.
The Principles Are a System
Forty-two Principles can look like forty-two separate ideas.
They are not.
They depend on one another.
Sometimes they reinforce each other.
Sometimes one prevents another from being taken too far.
Together they describe something larger than any individual lesson.
A way of approaching work.
A way of approaching responsibility.
And, increasingly, a way of approaching life.
Principles become useful when they stop being things you remember and become ways you naturally make decisions.
Curiosity Needs Humility
Curiosity asks:
Why?
Humility admits:
I may not already know.
Without humility, curiosity becomes performance.
We ask questions only to demonstrate what we know.
Real curiosity requires the possibility that the answer may surprise us.
Or contradict us.
Or prove us wrong.
That is why these Principles connect.
Curiosity keeps us searching.
Humility keeps us teachable.
Humility Needs Confidence
Humility does not mean believing you have nothing valuable to contribute.
You need enough confidence to make decisions.
To challenge assumptions.
To propose a better design.
To speak when something is wrong.
To lead.
The balance matters.
Confidence says:
"I believe this is the right direction."
Humility adds:
"Show me what I may have missed."
Together they create something stronger than either alone.
Truth Needs Courage
Truth Over Comfort sounds simple until the truth is expensive.
The project is late.
The design has a flaw.
The backup cannot be restored.
The metric is misleading.
The customer expectation cannot be met.
The mistake was yours.
Now truth requires courage.
It is easy to value honesty when honesty costs nothing.
Character appears when the truthful answer creates consequences.
Ownership Needs Truth
Ownership without truth becomes defensiveness.
If the outcome belongs to you, then you must be willing to understand the outcome as it actually exists.
Not as you intended it.
Not as the dashboard makes it appear.
Not as you hoped it would be.
Reality first.
Then responsibility.
Then improvement.
You cannot own an outcome you are unwilling to see clearly.
Ownership Needs Humility Too
Taking ownership does not mean claiming you can solve everything yourself.
Sometimes ownership means asking for help.
Escalating.
Calling the expert.
Admitting the problem exceeds your current knowledge.
Ownership is responsibility for the outcome.
Not ownership of every answer.
That distinction matters.
Curiosity Needs Judgment
Curiosity can take you anywhere.
Judgment decides whether you should go there now.
The rabbit hole will always be available.
There will always be another dependency.
Another optimization.
Another experiment.
Another interesting question.
Solve the real problem first.
Then decide which mysteries deserve more time.
Curiosity creates possibilities.
Judgment creates priorities.
Complexity Needs Purpose
Complexity is not automatically bad.
Some problems are genuinely complicated.
Some requirements demand sophisticated solutions.
The mistake is adding complexity without sufficient value.
Every dependency has a price.
Every abstraction has a cost.
Every component becomes something someone may eventually need to understand, operate, secure, recover, upgrade, or replace.
Build what the problem requires.
No more than necessary.
No less than responsible.
Automation Needs Understanding
Automation is powerful.
It removes toil.
Creates consistency.
Reduces repetitive mistakes.
Scales expertise.
It also scales whatever assumptions you put inside it.
A bad manual process performed once creates one problem.
A bad automated process can create thousands very efficiently.
Understand first.
Then automate.
Automation multiplies behavior. Make sure the behavior deserves multiplication.
Automation Needs Ownership
Automated does not mean ownerless.
Someone still needs to understand:
What it does.
Why it exists.
What happens when it fails.
How to stop it.
How to recover.
Who receives the alert.
Automation should remove unnecessary human effort.
It should not remove human responsibility.
Security Needs Design
Security added at the end is usually expensive.
Sometimes ineffective.
Protect what matters from the beginning.
Understand the data.
The access.
The trust boundaries.
The dependencies.
The recovery path.
The human behavior.
Security is not one component.
It is a property of the system.
Security Needs Usability
A control nobody can reasonably follow will eventually be bypassed.
People write down impossible passwords.
Create unofficial workflows.
Share accounts.
Move data somewhere easier.
Disable protections that constantly interrupt legitimate work.
That does not mean lowering security standards.
It means designing controls human beings can actually use correctly.
Good security protects people without requiring them to fight the system constantly.
Reliability Needs Failure
That sounds contradictory.
It isn't.
Reliable systems are designed by people willing to think seriously about failure.
What breaks?
What happens next?
What is redundant?
What is backed up?
What is monitored?
How do we recover?
How long will recovery take?
Has anyone tested it?
Design for failure because pretending failure will never happen does not make a system reliable.
It makes the failure surprising.
Backups Need Restore Tests
A backup is a promise.
A restore test verifies the promise.
Until then, you have hope.
This pattern appears everywhere.
A plan needs validation.
A design needs testing.
A theory needs evidence.
A procedure needs practice.
Confidence should be earned.
Metrics Need Context
Measure what matters.
But remember that measurement is representation.
The number is not the system.
Averages can hide spikes.
Percentages can hide populations.
Green dashboards can hide unhappy customers.
Performance metrics can reward behavior that damages the larger outcome.
Measure.
Then ask what the measurement actually means.
Standards Need Judgment
Standards create consistency.
They prevent teams from solving the same basic decisions repeatedly.
They encode experience.
But standards should not eliminate thought.
There will be exceptions.
New technologies.
Different risks.
Changed assumptions.
Use the standard.
Understand why it exists.
Then challenge it responsibly when reality no longer fits.
Documentation Needs Truth
Bad documentation can be worse than none.
Outdated instructions create confidence in the wrong answer.
Document what actually exists.
Update it when reality changes.
Include the strange parts.
Explain why.
Record limitations.
A document should reduce uncertainty.
Not preserve an old version of reality indefinitely.
Documentation Needs Curiosity
The best documentation often comes from remembering the questions you had before you understood.
Why is this here?
What does this connect to?
Which account does it use?
What happens if it fails?
Where are the logs?
How do I restore it?
What should normal look like?
Write for the person who will ask those questions next.
Teaching Needs Knowledge
You cannot teach what you do not understand.
Repeating instructions is not the same as transferring understanding.
Know the reason.
Know the tradeoff.
Know the failure mode.
Know where your knowledge ends.
Then teach honestly.
Teaching Needs Humility
The teacher does not always remain the expert.
Students grow.
Technologies change.
Someone you taught may discover a better method.
Good.
Let them teach you.
Teaching should create knowledge flow in both directions.
Teaching Needs Enablement
If you explain everything but never let someone act, you have created education without capability.
Eventually they need the keyboard.
The project.
The decision.
The presentation.
The responsibility.
Knowledge becomes capability through use.
Give people enough support to succeed and enough ownership for the success to belong to them.
Enablement Needs Standards
Helping someone succeed does not mean lowering expectations.
Give them the ladder.
Keep the height.
Training.
Tools.
Feedback.
Opportunity.
Context.
Guardrails.
Then let them climb.
Do not confuse making success possible with making success meaningless.
Trust Needs Consistency
Trust is not created by one impressive moment.
It accumulates.
You said you would do something.
Then you did it.
Again.
And again.
Your estimates were honest.
Your mistakes were acknowledged.
Your commitments meant something.
Eventually people stop wondering whether your word can be trusted.
That is a powerful form of infrastructure.
Trust Needs Truth
A comfortable lie can preserve trust for a moment.
Then destroy it completely.
Bad news delivered honestly may create a difficult conversation.
Hidden bad news creates a different question:
"What else aren't you telling me?"
Trust survives difficult truths far better than discovered deception.
Reputation Needs Quiet
If you constantly have to tell people how excellent you are, something is missing.
Let the work accumulate.
Let the customer speak.
Let the people you taught speak.
Let the systems you left behind speak.
A strong reputation is evidence gathered over time.
You do not need to narrate it constantly.
Excellence Needs Restraint
Good engineers can build many things.
Wise engineers know which ones should exist.
Every interesting idea does not belong in the current project.
Every possible feature does not belong in the product.
Every improvement does not justify the complexity.
Capability gives you options.
Judgment tells you which options to decline.
The Long View Needs Action Today
Thinking long-term does not mean postponing everything for some imagined future.
The future is built from today's decisions.
Document now.
Patch now.
Train now.
Test recovery now.
Remove the temporary workaround when it is no longer needed.
The long view changes what today's fifteen minutes are worth.
The Small Things Need the Big Picture
Sometimes the work is tiny.
Rename the variable.
Update the diagram.
Clean the equipment.
Write the note.
Return the call.
Fill the tank.
Those actions can look insignificant.
The big picture tells you why they matter.
Someone comes next.
Small acts of stewardship accumulate into reliable systems, trustworthy people, and healthy organizations.
The Big Picture Needs Small Things
Vision without execution is decoration.
You can talk about reliability forever.
Someone still needs to test the restore.
You can value documentation.
Someone still needs to write it.
You can value mentorship.
Someone still needs to sit beside the new engineer.
You can value integrity.
Someone still needs to tell the uncomfortable truth.
Principles become real through behavior.
Usually small behavior.
Repeated consistently.
Every Principle Has a Failure Mode
Almost any good idea can become harmful when separated from judgment.
Ownership can become control.
Curiosity can become distraction.
Standards can become bureaucracy.
Security can become obstruction.
Automation can scale mistakes.
Confidence can become arrogance.
Humility can become passivity.
Long-term thinking can become indecision.
Teaching can become dependence if ownership never transfers.
Simplicity can become inadequacy if the problem truly requires complexity.
That is why there are forty-two Principles instead of one slogan.
They balance one another.
No Principle Removes the Need to Think
This may be the most important warning in the entire collection.
Do not use Principles as substitutes for judgment.
There will be situations where two good principles appear to conflict.
Move quickly.
Be careful.
Simplify.
Add redundancy.
Trust people.
Verify.
Automate.
Slow down and understand.
Which one applies?
It depends.
Context matters.
Risk matters.
People matter.
Consequences matter.
Principles guide judgment.
They do not eliminate it.
A principle should improve your thinking, not replace it.
They Are Meant to Be Used Together
When facing a difficult decision, you may find several Principles standing in the room.
Tell the truth.
Own the outcome.
Protect what matters.
Measure what matters.
Understand the dependency.
Consider failure.
Keep the long view.
Ask what you are missing.
Solve the real problem.
Leave it better than you found it.
None alone gives you the complete answer.
Together they improve the question.
And better questions tend to produce better decisions.
This Is What Experience Becomes
Experience is not merely remembering more answers.
It is accumulating patterns.
Knowing which questions matter.
Recognizing risk.
Understanding consequences.
Seeing connections.
Knowing when the standard applies.
Knowing when the exception deserves consideration.
Knowing when to act.
Knowing when to stop.
Knowing when to ask for help.
Knowing how much you still do not know.
Principles are compressed experience.
They allow lessons to travel.
But They Are Not Laws
These forty-two Principles are not commandments.
They are not complete.
They are not immune from challenge.
They came from experience.
Mine.
The people who taught me.
The systems I worked on.
The mistakes I made.
The failures I witnessed.
The people I led.
The people who led me.
The customers who trusted me.
The questions I kept asking.
Another person's experience will add different lessons.
It should.
Improve Them
Challenge these Principles.
Test them.
Find the exceptions.
Refine the language.
Discover something I missed.
Add Principle XLIII if you need one.
I will not be offended.
In fact, that would prove several of the Principles worked.
Knowledge is meant to be shared.
Truth matters more than comfort.
Humility leaves room for better answers.
Curiosity never ends.
And everything worth inheriting should be improved when possible.
The System Is Alive
A philosophy that cannot tolerate new evidence eventually becomes dogma.
That is not what I want this to be.
Use these Principles.
Keep what works.
Understand why.
Challenge what doesn't.
Improve what you can.
Then pass the lessons forward.
The Principles themselves should be treated the same way we have treated every other system in this book.
Inherit them.
Understand them.
Test them.
Improve them.
Leave them better.
Closing Thought
Forty-two Principles are not forty-two answers.
They are forty-two reminders that good work requires more than technical ability.
It requires judgment.
Integrity.
Humility.
Curiosity.
Responsibility.
Care.
And the willingness to keep learning when experience would make it easier to stop.
Taken together, they ask something simple:
Do the work in a way that makes what comes after you stronger.
The Principles are not the answer. They are tools for becoming the kind of person who can keep searching for better ones.
Now It's Yours
If you have made it this far, I have spent a lot of time telling you what I think.
What experience taught me.
What mistakes taught me.
What good engineers taught me.
What bad systems taught me.
What leadership taught me.
What failure taught me.
What customers taught me.
What people taught me.
Now comes the important part.
What are you going to do with it?
Because the book cannot answer that for you.
Neither can I.
Eventually every lesson has to leave the page and become a decision.
Do Not Memorize This Book
That is not the point.
I do not expect you to remember forty-two Principles by number.
I don't expect you to quote them.
I don't expect you to agree with every sentence.
What I hope happens is much simpler.
Someday you are standing in front of a difficult decision and something in these pages comes back to you.
Maybe you ask:
What am I missing?
Maybe you stop before adding another dependency.
Maybe you test the restore.
Maybe you tell someone the uncomfortable truth.
Maybe you write the documentation before closing the ticket.
Maybe you let someone else keep the keyboard.
Maybe you ask one more question.
Maybe you spend the extra fifteen minutes.
That is enough.
Use What Helps
Some Principles will matter to you more than others.
That is natural.
Your work is different from mine.
Your career will be different.
Your mistakes will be different.
Your opportunities will be different.
Take what is useful.
Apply it.
Test it against reality.
If it makes you better, keep it.
If experience teaches you something more complete, improve it.
The goal is not loyalty to the book.
The goal is better judgment.
Challenge What You Disagree With
Please do.
If you read something here and think:
"That's wrong."
Good.
Ask why.
What experience led you somewhere different?
What assumption do you reject?
What exception have you encountered?
Can you explain the disagreement?
Can you support it?
Can you improve the idea?
That is exactly what curiosity should produce.
Agreement is not the price of admission.
Thinking is.
I would rather you challenge a Principle thoughtfully than follow it without understanding why.
Find Your Own Principles
These forty-two came from my experience.
You will collect your own.
Maybe you already have.
Things a parent taught you.
A teacher.
A manager.
A coworker.
A customer.
A failure.
A success.
A terrible project.
A great team.
A mistake you promised yourself you would never make again.
Write them down.
You may be surprised how many decisions in your life are already guided by lessons you have never formally named.
Give them names.
Think about them.
Test them.
Refine them.
Know Where Your Principles Came From
A principle without context can become a superstition.
Understand why you believe what you believe.
Maybe you value documentation because you once inherited a system with none.
Maybe you value testing because a failed deployment taught you the cost of assumptions.
Maybe you value honesty because someone once lied to you.
Maybe you value mentorship because someone took the time to teach you.
Maybe you value preparation because you once needed a recovery plan that did not exist.
The story matters.
It reminds you what problem the Principle was trying to solve.
Some Lessons Are Expensive
I would love to tell you that reading about someone else's mistakes allows you to avoid all of your own.
It doesn't.
You will make mistakes.
Some will be embarrassing.
Some expensive.
Some painful.
Some will become stories you tell years later.
Learn from them.
The price has already been paid.
Do not waste the purchase.
A mistake becomes more expensive when you pay for the lesson and refuse to learn it.
Borrow Experience Whenever You Can
You do not have enough time to make every mistake personally.
That is one reason we teach.
Listen to people who have been there.
Read the incident report.
Study the failure.
Ask the experienced engineer what they would do differently.
Ask the customer what actually hurt.
Ask the person leaving what nobody documented.
Ask the new person what makes no sense.
Borrow experience.
Then add your own.
Do Not Confuse Age With Wisdom
Time produces experience.
It does not guarantee reflection.
Someone can repeat the same year twenty times.
Another person can learn enormously from five.
The value is not simply how long you have been doing something.
It is whether you remained awake while doing it.
Did you ask why?
Did you examine the result?
Did you change?
Did you teach?
Did experience modify your judgment?
Years are counted automatically.
Wisdom is not.
Your Career Is Not a Straight Line
Mine wasn't.
Yours probably won't be either.
Skills transfer in strange ways.
A lesson from one job appears ten years later in another.
A communication skill becomes a leadership skill.
A support problem becomes an engineering principle.
A failed project becomes an architecture standard.
A call center becomes a lesson about multiplying people.
You cannot always see which experiences will matter while you are living them.
Pay attention anyway.
Take the Strange Opportunity
Some of the most valuable experiences begin with something outside the expected path.
A project nobody else wants.
A technology you have never used.
A customer problem outside your specialty.
A chance to teach.
A chance to lead.
A chance to build.
A chance to start over.
Not every opportunity deserves yes.
But do not become so protective of the career you planned that you miss the career experience is trying to give you.
Become Useful
There are many ways to measure a career.
Titles.
Salary.
Certifications.
Promotions.
Projects.
Awards.
Those things can matter.
But there is another measure I value greatly.
Are you useful?
When something difficult happens, do people trust you?
Can you help?
Can you find the answer?
Can you make the situation clearer?
Can you calm the chaos?
Can you teach someone?
Can you improve the system?
Can you leave the problem smaller than you found it?
Useful people create value wherever they go.
Become Trustworthy
Competence matters.
Character matters longer.
People will eventually forget many technical details about projects you worked on together.
They will remember whether they trusted you.
Did you tell the truth?
Did you keep your word?
Did you admit mistakes?
Did you give credit?
Did you show up when things were difficult?
Did you protect what they trusted you with?
Did you treat people well when you did not need anything from them?
Your technical reputation and your human reputation eventually become the same reputation.
Learn to Say "I Don't Know"
You will need this sentence.
Use it.
Then add:
"But I'll find out."
Or:
"Let's find out."
Those words can carry you through an entire career.
They protect you from pretending.
They invite collaboration.
They preserve curiosity.
They make room for learning.
You do not need to possess every answer.
You need to remain capable of finding better ones.
Learn to Say "I Was Wrong"
You will need this sentence too.
Use it quickly.
Do not spend three meetings defending something you already know is incorrect.
Do not make other people fight through your ego to reach the truth.
"I was wrong."
Then:
"Here is what I learned."
That is not weakness.
That is maintenance.
You are correcting your own model of reality.
Good engineers do that constantly.
Good people should too.
Learn to Say "You Were Right"
This one matters more than people realize.
Someone challenged you.
You disagreed.
The evidence arrived.
They were right.
Tell them.
Not reluctantly.
Not:
"Well, technically..."
Just say it.
"You were right."
People remember leaders who can do that.
It tells them that truth actually matters more than hierarchy.
Learn to Say "Thank You"
Nobody builds alone.
Someone gave you time.
Someone answered your question.
Someone reviewed the code.
Someone opened the door.
Someone took a chance on you.
Someone covered the outage.
Someone taught you something.
Someone told you the truth when it would have been easier not to.
Notice.
Say thank you.
Competence without gratitude becomes entitlement.
Teach Before You Leave
At some point, you will know something other people need.
Do not wait until your final week to transfer it.
Teach while you are still there.
Document while the details are fresh.
Bring someone into the meeting.
Explain the strange configuration.
Let someone else run the procedure.
Create another expert.
You should not need a frantic knowledge-transfer meeting before every transition.
Knowledge transfer should have been happening all along.
Make Yourself Replaceable
This sounds dangerous to some people.
It isn't.
If you are the only person who can perform your current responsibilities, you may feel secure.
You may also be trapped.
You cannot move.
The organization cannot move.
Every vacation becomes an escalation path.
Every promotion creates a coverage problem.
Teach people.
Automate.
Document.
Build capability.
Make yourself replaceable at yesterday's work.
That creates room for tomorrow's.
Help Someone Pass You
At some point, someone you helped may become better than you.
Faster.
More knowledgeable.
More accomplished.
More senior.
Good.
Do not move the finish line because they are getting close.
Do not withhold the final lesson.
Do not suddenly become protective of status.
Help them.
Their success does not erase yours.
It may be part of it.
Build Something You Will Never See Finished
Some work is larger than one career.
A culture.
An institution.
A body of knowledge.
A person.
A family.
A profession.
You may contribute without seeing the final result.
Do it anyway.
Plant things whose shade belongs to someone else.
Not every return needs to arrive while you are still standing there.
Leave Evidence That You Cared
The person who comes after you may never know you.
But they will encounter your decisions.
They will see whether the documentation exists.
Whether the names make sense.
Whether the temporary workaround was cleaned up.
Whether the recovery procedure works.
Whether someone thought about failure.
Whether knowledge was preserved.
Whether the system feels cared for.
You leave fingerprints on work even when your name is removed.
Make them good ones.
Write Things Down
Memory is temporary.
Write.
Document the system.
Document the decision.
Document the failure.
Document the lesson.
Write the story.
Write your Principles.
Someone may need them later.
You may need them later.
This entire book exists because experiences that lived in my head were eventually written down.
Until then, they could travel only as far as I could personally carry them.
Now they can go somewhere without me.
That is the point.
Your Version Will Be Different
If you eventually write your own forty-two Principles, I hope they are not these.
Some may overlap.
Others should not.
Your experience should add something.
Your generation should encounter problems mine did not.
Your technology will be different.
Your world will be different.
Your answers should evolve.
If every generation merely repeats the previous one, nobody is learning.
Inheritance is the starting point.
Not the finish line.
Add the Forty-Third
I called this book Solve for 42.
Forty-two is where this collection ends.
It does not need to be where yours does.
Maybe experience gives you forty-three.
Maybe seventy.
Maybe seven principles are enough.
The number is not important.
The reflection is.
Know what you believe.
Know why.
Remain willing to change it when reality teaches you something better.
Then Give Yours Away
Do not keep the lessons only for yourself.
Tell the story.
Teach the engineer.
Mentor the new employee.
Write the runbook.
Share the failure.
Explain the mistake.
Publish the idea.
Help someone avoid paying the same price for knowledge you already purchased.
Knowledge becomes more valuable when it moves.
You Are the Next Person
Throughout this book I have repeatedly talked about the next person.
Leave documentation for the next person.
Build recovery for the next person.
Remove mystery for the next person.
Teach the next person.
Prepare the system for the next person.
There is something I should make explicit now.
Sometimes...
You are the next person.
You inherited this book.
You inherited these stories.
You inherited these mistakes.
You inherited these lessons.
For a little while, they are yours.
What happens next is no longer up to me.
The Handoff
That is what this section really is.
A handoff.
I have carried these lessons as far as I can inside these pages.
Now you decide whether they travel farther.
Use them.
Challenge them.
Improve them.
Teach them.
Replace them when you discover something better.
Add your own.
And when someone eventually inherits what you know...
Give them a better starting point than you had.
You inherited someone else's lessons. Add your experience to them, then leave the next person more capable than you were when they reached you.
Founder's Commentary
What I Hope I Leave Behind
I started writing these Principles because I had accumulated lessons I did not want to lose.
Some came from success.
Many came from mistakes.
A few were expensive.
Some were taught to me by people whose names I still remember.
Others came from people who probably never realized they were teaching me anything at all.
Over time, they became part of how I work.
How I make decisions.
How I lead.
How I solve problems.
How I try to treat people.
Writing them down forced me to ask something I had not really asked before.
What do all of these lessons add up to?
I think I know now.
It Was Never Really About Technology
Technology is where much of my experience happened.
It gave me the problems.
The failures.
The puzzles.
The customers.
The teams.
The late nights.
The recoveries.
The opportunities to build things that had not existed before.
I love technology.
I still find it fascinating.
I hope I always will.
But somewhere while writing this book, I realized that most of the lessons I cared about were not really technical.
Tell the truth.
Keep your word.
Admit what you don't know.
Own the outcome.
Be humble.
Teach people.
Protect what matters.
Help others succeed.
Stay curious.
Leave things better than you found them.
You don't need a computer to do any of those things.
The Technology Was the Classroom
That may be the simplest way I can explain it.
Technology was the classroom.
It gave me immediate feedback.
Bad assumptions eventually failed.
Poor preparation eventually mattered.
Missing documentation eventually hurt someone.
Complexity eventually sent its bill.
Trust eventually compounded.
Teaching eventually multiplied.
Curiosity eventually found something.
The systems were teaching me about more than systems.
I just didn't always realize it at the time.
I Have Been Lucky
I have had opportunities to work with extraordinarily intelligent people.
I have worked on difficult problems.
Large systems.
Important systems.
Systems where failure mattered.
I have been trusted with responsibility.
I have been given opportunities to lead.
To teach.
To build.
To fail.
To recover.
And to try again.
Not everyone receives the same opportunities.
I know that.
So I believe there is a responsibility attached to having them.
Learn something.
Then give something back.
I Am Still Learning
Nothing about reaching Principle XLII means I am finished.
I will make another mistake.
Probably more than one.
I will encounter something I do not understand.
Someone will challenge something I believe.
Technology will change.
Experience will add another lesson.
Maybe something in this book will eventually need refinement.
Good.
That means I am still paying attention.
I would be much more concerned if I reached a point where nothing could change my mind anymore.
These Are My Forty-Two
They are not the forty-two.
They are mine.
The lessons that survived long enough to become important to me.
If I wrote this book again twenty years ago, it would be different.
If I am fortunate enough to revisit it twenty years from now, I hope it would be different again.
Because I hope I will have learned something.
That is the bargain.
We preserve what experience has taught us without pretending experience is finished teaching.
I Don't Need You to Agree With Me
You may disagree with some of this book.
You probably should.
Your life is not mine.
Your career is not mine.
Your failures will not be mine.
Your conclusions do not have to be mine.
What I hope is that something here makes you think.
Maybe one story changes a decision.
Maybe one Principle prevents a mistake.
Maybe one question follows you into a meeting.
Maybe you teach something instead of keeping it to yourself.
Maybe you stop and ask what you are missing.
Maybe you leave one system, one team, or one person better than you otherwise would have.
Then writing this was worth it.
The People Matter Most
Systems are replaced.
Code is rewritten.
Servers are retired.
Companies change.
Products disappear.
Technologies that once seemed permanent become historical footnotes.
People carry things forward.
A lesson.
A standard.
A habit.
A story.
A way of thinking.
Confidence someone helped them discover.
An opportunity someone gave them.
Knowledge someone took the time to share.
That is why, looking back, the people matter more to me than the technology.
The technology gave us something to build together.
The people made the work worth remembering.
I Hope Someone Had an Easier Day
Maybe that is too small a measure for a life's work.
I don't think so.
I hope someone inherited a system and found the documentation.
I hope someone avoided an outage because we planned for failure.
I hope someone went home on time because we automated the repetitive work.
I hope someone felt confident because I took the time to teach them.
I hope a customer received something better than they expected.
I hope someone got an opportunity because I opened a door.
I hope an engineer solved a problem without calling me because I taught them enough that they didn't need to.
Those things count.
They count a lot.
I Hope I Filled the Gas Tank
My grandmother's lesson stayed with me.
A job worth doing is a job worth doing right the first time.
Finish the job.
Clean up.
Put things away.
Prepare for the next person.
Fill the gas tank.
That lesson turned out to be much larger than a lawn mower.
It became documentation.
Preparation.
Stewardship.
Responsibility.
Consideration for whoever comes next.
Maybe this book is another version of filling the gas tank.
I learned these lessons.
I used them.
Now I am leaving them here for the next person.
There Is No Final Answer
The joke behind 42 works because the answer is useless without understanding the question.
Life is considerably more complicated than one question anyway.
There will always be another variable.
Another perspective.
Another unknown.
Another person.
Another consequence.
Another question.
I am comfortable with that.
I don't need a final answer.
I would rather remain curious.
What Was It All For?
At the end of Principle XLI, I asked that question.
After everything we have built...
Everything we have learned...
Everything we have taught...
Everything we have protected...
Everything we have left behind...
What was it all for?
I don't think the answer is a title.
Or a salary.
Or a system.
Or a company.
Or a product.
Or even a book.
Those are things we do along the way.
The answer, for me, is what changed because we were here.
Did we help?
Did we teach?
Did we protect?
Did we build?
Did we make someone's path easier?
Did we leave knowledge behind?
Did we create something another person could build upon?
Did we make the small part of the world entrusted to us a little better?
If the answer is yes...
That is enough for me.
Thank You
If you made it all the way here, thank you.
You gave me something valuable.
Your time.
I hope I respected it.
I hope somewhere in these pages you found something useful.
Something worth arguing with.
Something worth remembering.
Something worth teaching.
Something worth improving.
And someday, perhaps, something worth passing forward.
I have carried these Principles as far as I can inside this book.
They belong to you now.
Solve for 42
Ask the question.
Follow the evidence.
Tell the truth.
Own your work.
Keep your word.
Protect what matters.
Prepare for failure.
Stay humble.
Teach what you learn.
Help people succeed.
Remain curious.
And remember that someone comes after you.
You will not solve everything.
You were never supposed to.
Just take your turn.
Carry the work for a while.
Care for it while it is yours.
Add what you can.
Then hand it forward.
A little stronger.
A little clearer.
A little easier to understand.
A little better prepared for whoever comes next.
That is my answer.
It may not be yours.
I hope you find yours.
And when you do...
Share it.
Now go leave something better behind.
Related Principles
Continue the idea.
These Principles share themes with Principle XLII.
Principle XL
Enable Others to Succeed
Leadership through coaching, delegation, trust, psychological safety, parenting, mentorship, and developing independence.
Read Principle XL →Principle XXIX
Truth Over Comfort
Honesty when truth is inconvenient, difficult conversations, reality over preference, and ethical courage.
Read Principle XXIX →Principle XXXIV
Be Humble
Humility, listening, correction, disagreement, learning from others, and confidence without ego.
Read Principle XXXIV →Principle XI
Consistency Builds Confidence
Predictability, trust, dependable behavior, stable patterns, and confidence built through consistency.
Read Principle XI →