My daughter watches these videos.
I have no idea what she makes of a man in a Peaky Blinders cap telling strangers to nap at their desks. But she watches. She laughs. And I can tell she is proud her daddy is on YouTube.
The other day she asked a question:
“Daddy, who are engineers?”
Easy one. “Engineers are people who solve problems.”
She thought about it.
Then said: “Aha. You mean like mom.”
Twenty years, a senior title, a newsletter about engineering — and I just got stunned by a kid’s definition.
She’s not wrong. Kids don’t read titles. All she sees is behavior. There was a problem. Someone came. Now there isn’t one.
But this article is not about mom. Mom is fine. Mom has a 100% incident-resolution rate and has never said “let’s take this offline.”
This is about the other word in her sentence. Engineer.
I went to war for that word once — Call Me En-Gi-Neer — refusing to be called a “resource.” That was about the title. This is about what lives underneath it.
And the first thing to know: nobody is born an engineer. Have you ever seen an engineer being born? Zero output, no logs, crying incidents at 3 a.m. Completely normal. You are born a baby. An engineer — you become.
Engineer is not a job title either.
Anyone can print the title.
The behavior is the test.
What engineers actually do
1. You solve the problem, not the request. The ticket says add a button. You can blindly add the button — that is typing. Or ask why, and find the user clicks it forty times a day to work around a broken process. Fix the process, not the button.
2. You don’t count on the ideal scenario. You count on the real one. The ideal scenario has a greenfield repo, clear ownership, and a database that has never met a user. Nobody works there. The real job: a legacy system whose author left in 2019, two teams who each think the other owns it, and you in the middle. A fix that requires ideal conditions is science fiction.
3. You own the blast radius. “It works on my machine” is the most honest lie in engineering. It always works on your machine. The job is done when it survives a stranger’s machine running the sequence you swore nobody would run. Is your catch block real, or the empty kind that swallows the exception and ships it downstream to a stranger? Working once is a trick. Surviving an angry user is the job.
4. You make the problem harder to repeat. Restarting the service is easy. Ticket closed. See you next Friday. Same fire. Finding the leak is harder, but then the fire is gone for good. Restart-only never fixes the cause, so the cause keeps needing you — some people do that on purpose and call it job security. But babysitting the same service every Friday is not ownership. It is a hamster wheel with pager duty.
5. You leave it more understandable than you found it. Someone inherits every system you touch. Usually you, six months older, wondering what kind of idiot wrote this. Then Git tells you. It was you. You named the critical variable temp2. The honest name, the why-comment, the real README — none ships a feature, all of it decides whether the next person needs hours or archaeology. If only you understand it, it is not clever. It is unfinished.
You do not stay an engineer by default
You do not become one once and keep the badge. Every year the tools change, the abstractions move, the old certainty expires. Staying relevant is not a motivational poster. It is maintenance. The moment you stop learning, you do not become senior. You become legacy. People talk about you in past tense.
And of course, it comes with defects.
Being an engineer is not a gift. It is a condition. You cannot switch it off.
You see the loose cable. The vague sentence. The menu with three fonts. You did not ask to. You just can’t stop.
“I’ll just take a look” is how it gets past midnight — six hours gone, the whole house asleep long ago, and you still at the laptop.
And you are a magnet for problems nobody owns. You are the person who can’t ignore them. Doesn’t matter that it’s not your expertise. Congrats. You are now cross-functional.
Good work is invisible until someone else takes the credit
Here is the strange part: when you do it well, often nothing happens. The outage that did not occur. The bug that died in review. No fire, because you put it out before it started.
Nobody throws a parade for the bridge that stood. The bridge that falls gets a task force, a logo, and a senior director.
So invisible work still needs a receipt. Not fireworks — just a trace. Write the note. Close the loop. Make it findable. Otherwise someone finds your work six months later, renames it a “stability initiative,” and puts it on slide 14.
Being humble is fine. Becoming furniture is not.
The title and the work do not always travel together
You know a Principal whose last real commit is two years old. Ask what he shipped lately and you get a slide about enablement. He does not solve problems anymore — he enables solutioning at scale, which is Latin for “attends meetings.”
And you know the reverse. The electrician walks in, listens for thirty seconds, and makes the face — the one that means: I know exactly who did this, and legally I cannot say what should happen to him. Then he fixes it, explains it in two sentences, and charges accordingly. No title. All behavior.
Same in software: the support engineer who finds the pattern behind twenty “random” tickets, the junior who fixes the flaky test everyone else just mutes. Nobody gave them the title. They simply are.
The title without the behavior is a costume. The behavior without the title is just an engineer who has not been processed by HR yet.
Earn the word
My daughter will learn the title eventually. School will teach her the spelling, LinkedIn the prefixes, and some budget wizard with a spreadsheet will teach her the word “resource.”
But the behavior she has already seen: someone notices the broken thing, fixes it so it stays fixed, owns what happens next, no press conference. She thinks that is normal. She has no idea how rare it is — and I am not telling her. Let her find out in her first refinement session, like the rest of us.
The title can wait. Titles are patient — they live in email signatures and LinkedIn headlines. The behavior is due every time a problem occurs and you are standing closest.
Earn the word. The pronunciation we already settled.
By order of thebeanengineer.com — Be an engineer. 🚀.