Who are you without the answer?

A road sign told me one thing. Google Maps told me another. I believed the screen.

A note before you read. I used AI to pressure-test the argument in this essay. Not to write it. To challenge it. I will tell you where it surprised me and where it failed me, because that is the honest way to write about this subject.

---

We decided to drive to the sea side, to get some of that majestic sound of the sea. As I was driving, I found myself thinking about the state we are living in today, the threat of full automation, and that strange sense that technology has started to feel a bit like religion, where every day we go looking for some sort of answer. I understood that my answer on that particular day was simply to get to the sea side. But I kept bothering myself with the question of when, exactly, we decided to start looking for our answers in technology instead. Especially the online kind. And how, for some reason, none of us can really imagine our lives now without most of the platforms we use every day.

I remember the ticket number before I remember the problem.

That is the strange thing about the service desk years. I would write it down on a slip of paper, the number, the issue, the user’s name, the building they sat in, and then I would run. Up two flights, across the car park, into a department I had never set foot in before that morning. I would teach someone how Outlook worked. I would show them a trick to make the phone on their desk stop confusing them. I would explain, in plain words, what we were even there for, because half the time nobody had told them.

It was stressful. I am not going to pretend otherwise. But there was a kind of satisfaction in it that I have not found many places since. Someone had a problem. I had an answer, or I could find one fast enough that it didn’t matter. They got back to work. I moved on to the next slip of paper.

I still remember the texture of those slips. Pale yellow carbon paper, the kind that left a faint copy underneath when you pressed too hard with the pen. The smell of the stairwells, somewhere between dust and old carpet. The particular sound a desk phone made when it had been left off the hook too long, a flat angry tone that meant someone, somewhere, had given up waiting and walked away from their own desk in frustration. You learn a building by its noises long before you learn it by its floor plan.

The hardest days were the loud ones. The head of the call centre shouting because half the floor had lost phone signal at once. That meant getting on to the telephony team, talking them through what I could see from my end, then physically walking into the IT room to trace where the line had dropped. Patch cables. Cold metal racks. The smell of dust burning faintly off the back of an old switch. People skills and troubleshooting, stitched together so tightly you couldn’t separate them even if you tried.

I was good at it because I knew things. Not everything. But enough, and fast enough, and I could find the rest before anyone noticed I hadn’t known it five minutes earlier.

I think that is where it started. The quiet rule nobody says out loud in this industry. You do not want to be the one who does not know.

We talk about being lifelong learners. We put it on our LinkedIn headlines. But underneath the language of curiosity there is something less comfortable, which is that not having an answer, in the room, in the moment, in front of the person who is waiting on you, feels like a small failure of self. Even when nobody says anything. Even when nobody is counting.

The cost of not knowing changes shape depending on the room you are in. Among close friends, not knowing something usually just gets you a gentle joke and the moment moves on. At work, the joke has a bit more edge to it. In a large enough group, in front of enough people, not knowing the answer can quietly turn you into the joke itself, the one the room remembers, long after anyone remembers what the actual question was. I think most of us are reacting to that third version far more than we admit, even in rooms that never come close to it.

I have sat in enough meetings now to recognise the performance when I see it. Someone gets asked a question they do not have a good answer to, and instead of saying so, they reach for a sentence built entirely out of confidence and nothing else. We are aligned on that. It is on the roadmap. Let me circle back. None of those sentences contain information. All of them are doing the same job, which is buying time so the room does not notice that the person speaking does not know. I have done it myself, more than once, and I remember exactly how it felt each time, which was nothing like confidence and everything like holding my breath.

It has shifted again recently, in a way I find harder to sit with. It is no longer uncommon to be in a meeting and watch someone quietly type a question into a chatbot mid conversation, while the rest of the room waits in a silence that nobody quite names. I find it strange, possibly because I am older than the habit. If you book a meeting, I assume the people in the room came to share their own thinking with each other, not to outsource the thinking to a screen while everyone else watches. A fair number of meetings now seem to be less about what anyone in the room actually knows, and more about who can ask the model the sharpest question fastest. I am not sure that is a worse skill to have. I am fairly sure it is a different meeting than the one we agreed to have when we put it in the calendar.

What strikes me, looking back, is how much of leadership in tech gets built on top of that performance rather than underneath it. We reward the appearance of certainty far more often than we reward the harder, slower work of actually finding things out. A leader who says I do not know yet, give me until Thursday, often reads as weaker in the room than a leader who guesses with conviction and happens to be wrong. We have built whole cultures around rewarding the wrong half of that trade.

I carried that pressure for a long time before I noticed I was carrying it.

By the time I was leading the team I had worked alongside for three years, it had become something closer to an obligation. I read every procedure. I sat with other departments to understand how their work actually moved, not how the org chart said it moved. I gathered feedback from my own people and I actually listened to it, which is a smaller thing than it sounds and a bigger thing than most leaders manage. I pushed them hard. I gave them flexibility in return, time off when they needed it, early finishes when the work allowed it. That part felt fair. What never felt fair was the thing underneath it. The constant low hum of needing to be ready for any question that might land on my desk. Not because anyone demanded it of me. Because I had decided, somewhere back on the service desk, that this was what being trusted looked like.

Then I became a manager properly, and the maths stopped working.

You cannot know everything. Not because you are not capable, but because the surface area of the job grows faster than any one person’s memory can cover it. I had to learn to delegate, and I want to be precise about what that actually meant, because it is not the thing people assume. Delegating is not handing off a task because you are busy. It is asking, every single time, whether the person you are handing it to is being set up to succeed or quietly being set up to fail, and being honest with yourself about which one it actually is. I got that wrong more than once. I will not pretend I always called it correctly. But the discomfort of getting it wrong taught me more about leadership than any answer I ever had ready in a meeting.

There was a particular kind of fear underneath delegation that I do not think gets talked about enough. It is not really a fear that the work will be done badly. It is a fear that you will be exposed as someone who did not actually need to be the one holding all the answers in the first place. If someone else can solve the problem without you, what was all that knowing for. I think a lot of managers hoard answers without realising that is what they are doing, because letting them go feels uncomfortably close to admitting they were never as essential as the job title implied. I had to sit with that discomfort directly before I could let go of anything properly. It did not happen once and stay finished. I had to do it again every time the team changed, every time a new person joined who expected me to have the answer simply because of where I sat in the org chart.

What kept me afloat in those years was that I was always taking knowledge in. From people who would sit beside me and show me, often too quickly, often without patience, because they had their own ticket queue piling up. I learned to pay close attention in those moments because I knew I might not get a second explanation. From books. From the web, back when pages still loaded slowly enough that you had time to think about the question again while you waited.

And then, somewhere around 1998, a colleague said something that changed the shape of all of it. Go to Google. Just Google it.

I was on AltaVista at the time. It worked, mostly. It was not elegant. Then Google arrived, and the first time I typed in an error message exactly as it appeared on screen and found someone, anywhere in the world, who had hit the same wall and written down how they got past it, something in me relaxed. Not because I no longer needed to know things. Because I realised I was not alone in not knowing them. Somebody out there had already paid the cost of figuring it out, and had chosen, for nothing, to leave the answer behind for the next person.

There is a generosity in that I think we have stopped noticing because it became so normal. An entire generation of engineers learned their craft not from manuals or courses but from strangers who had hit the same wall at two in the morning and decided, for nothing, to write down how they climbed over it. Forums full of people answering questions they had no obligation to answer. It was one of the strangest and best things the internet ever produced, and we absorbed it so completely that within a decade it had stopped feeling like generosity at all. It just felt like how information worked.

For a stretch of years, into the mid 2000s, it was completely ordinary to be sitting in a meeting and hear someone say, hang on, let me Google it. And the room would wait, comfortably, while someone found the answer on a machine instead of in a colleague’s head.

I noticed the shift without naming it at the time. We were spending more time searching than asking. Not because asking had stopped working. Because searching was faster, and we were all under the same pressure to move quickly, and if the answer was already sitting out there for free, why would you spend someone else’s time getting it?

I do not think that decision was wrong, exactly. I think it was the first domino, and we did not see the rest of the row yet. What got quietly lost in that trade was not the answer. It was the conversation that used to happen on the way to the answer. The version where you turned to the person next to you and the act of explaining the problem out loud was half of how you solved it. You do not get that from a search box. You get the answer and skip the explaining entirely, and for a long time none of us thought that was a cost worth naming.

Even so, searching was still fundamentally an act of asking. You typed the question yourself. You chose the words. You read several answers, weighed them against each other, and decided which one fit your actual situation, because the page in front of you was a list of other people’s attempts, not a single confident voice telling you the answer was settled. There was still a small act of judgment sitting in the middle of it, even if we stopped noticing it was there.

Then Covid arrived, and whatever was left of the habit of walking over to someone’s desk got removed entirely, for years, for some people permanently. I sat at home trying to get things done with the help of strangers’ generosity online, the same generosity that had started with that first AltaVista search, just compounded a thousand times over by then. There was real autonomy in it. I will not take that away from the period. But I missed the version of work where solving a problem meant standing next to another human being while you did it.

I tried to claw a little of that back with the teams I led. Virtual lunches. Coffee breaks that were allowed to be aimless. Social time that had nothing to do with delivery dates. It worked, I think, because we were all adults who already remembered what an office felt like, so we knew what we were trying to recreate. Remote work gave us a freedom none of us had been offered before. I will defend that part of it without hesitation.

What I noticed, slowly, over those years, was that the questions people brought to a video call were different to the ones they used to bring to a desk. On a screen, you arrive with the question already mostly formed, because the cost of opening a call feels higher than the cost of wandering over and thinking out loud on the way. Something about distance makes you arrive pre-edited. I do not think that is a worse way to ask a question. I think it is a narrower one. The half formed, still figuring it out version of a problem, the one you used to talk through on the walk between two desks, mostly stopped happening, because there was no walk left to have it on.

But I also remember sitting in my car one ordinary morning, stuck in the kind of traffic that used to be invisible to me because I had simply accepted it as the cost of having a job, and realising, properly realising, how much stress I had carried for decades without ever once putting it down on the table to look at.

Then came the models.

We built machines that could predict, with a kind of fluency that genuinely startled people who had spent their whole careers around computers, what word should come next. The frenzy that followed was enormous. Doom on one side, salvation on the other. Neither one fully arrived. What arrived instead, quietly, almost politely, was something else entirely. Tools built so that you would never again need to hold the answer yourself. Intelligence, metered out on demand, priced by the token, available the moment you needed it and gone the moment you closed the tab.

That small act of judgment I mentioned, the weighing of several answers against your own situation, mostly disappears here. A model gives you one voice, delivered with total confidence regardless of whether it deserves that confidence, and the format itself nudges you toward accepting the first answer rather than comparing several. I do not think this happened because anyone sat in a room and decided to remove judgment from the process. The business underneath these tools rewards speed and fluency, because speed and fluency are what keep you coming back to pay for the next query. Nobody designed it to make us less careful. It just turns out that careful is slower, and slower does not retain a subscriber the way fast does. That is the system working exactly as its incentives point it, with no one person to blame for the shape it has taken.

I want to be honest about my own relationship with this, because the Mirror Test only means something if you actually look in it. I use these tools. I use them to help me forecast, to map out possibilities I might not have reached for on my own, and even when the output is mundane, it is genuinely useful for stretching my imagination further than it would stretch alone. That part is real and I am not going to write an essay pretending otherwise.

I think the honest version of this is closer to medicine than most of us want to admit. You do not take ten paracetamol at once because one worked well for the last headache. You take the dose that is actually needed, you read the packet, you ask someone who knows more than you if you are not sure, and you stay alert to what mixing it with everything else in your day might do to you. Nobody thinks of that as restriction. We think of it as basic care for something powerful enough to do real harm if you stop paying attention to how much of it you are taking. I do not think we have built that same instinct yet for how much thinking we are handing over in a single day, and I include myself in that.

But I do not think we are using these tools the way we tell ourselves we are.

There is a difference between offloading a cognitive task because it frees you up for harder thinking, and offloading it because not doing the thinking yourself has simply become the path of least resistance. The first is a tool. The second, I think, is dependency wearing the tool’s clothes. And the second one does not announce itself. It feels exactly like convenience right up until the moment you notice you have stopped being able to tell the difference between the two.

I have sat with teams while they worked through exactly this tension, and it rarely resolves cleanly. Someone will say the model saved them four hours on a problem they would have solved themselves anyway, slower. Someone else will admit, quietly, that they no longer try the problem before reaching for the tool, which is a different thing entirely. Both of those people think they are describing the same behaviour. They are not. One of them is augmenting judgment they already have. The other is letting the judgment atrophy without noticing, because atrophy is slow and convenience is immediate, and we are creatures who respond to the immediate thing far more readily than the slow one.

The engineers I respect most right now are not the ones refusing the tools out of principle. They are the ones who can tell you, specifically, which parts of their thinking they have handed over and which parts they have deliberately kept for themselves, and why. That distinction takes effort to maintain. Most of us, myself included on certain days, let it blur because maintaining it is tiring and the tool does not ask you to maintain it. It just answers.

I keep returning to one question lately, and it will not leave me alone.

What happens if we get to a point where none of us actually knows the answer anymore? Not because we are incapable. Because we stopped needing to be the one who held it.

What does it mean when a software engineer can no longer explain why a repository is structured the way it is, because the structure was generated rather than understood. What does it mean when a project manager cannot tell you why a project needs to happen in a particular order, only that the plan said so. What does it mean when everything around you works, every system, every workflow, every dashboard, but the why of it has become a black box you have quietly agreed never to open.

I think about the engineers coming up now, the ones a few years into their careers, the way I once was on that service desk floor. A lot of what made me competent back then was not talent. It was repetition. I broke the same kind of thing enough times that I started to recognise its shape before it fully broke. If the tool gets there first every time, what does that engineer end up recognising. What pattern gets to live in their hands instead of in a model they cannot see inside. I do not know the answer to that yet. I am not sure anyone does. But I notice that most conversations about this stop at productivity, how much faster the junior engineer ships, and almost never reach the second question, which is what they are no longer building inside themselves while they ship it.

The same question sits inside leadership too, not just inside the codebase. A manager who has never personally wrestled with a hard tradeoff, because the model summarised the tradeoff for them in a clean paragraph, is going to have a thinner instinct for the next hard tradeoff that does not come with a clean paragraph attached. Judgment is built the slow way, through friction, through getting it wrong in a smaller room before you have to get it right in a bigger one. I worry we are quietly removing the smaller rooms.

There is a quieter cost too, one that sits between people rather than between a person and a machine. When the answer used to come from a colleague, something passed between you in the asking. A small debt, a small trust, a reason to remember each other’s names and check in later on whether the fix had held. When the answer comes from a model instead, that exchange simply does not happen. Nobody owes anybody anything. The problem gets solved and nothing relational gets built on top of it. I do not think that is a tragedy on its own, in any single instance. But I think it adds up, across thousands of small exchanges a year, into teams that know how to solve problems together far less often than they used to, because they have quietly stopped needing each other to do it.

Does any of this make you feel secure. Does it make you feel in control. I do not think it does, even when we perform confidence about it in meetings.

And there is a harder question sitting underneath that one. If you no longer know the answer yourself, how do you know whether the answer you have been handed is even true. Verification itself becomes a chore, something we skip because we are tired, because we are behind schedule, because the thing on the screen looks plausible enough and plausible has quietly become our new bar for true.

It was on the way back from that same drive to the sea that I got the clearest possible proof of this, in a way I am slightly embarrassed to put in writing. There were signs along the road home, more than one, telling us the route ahead was closed. One of them said, plainly, do not rely on Google Maps. The app on the dashboard disagreed. It showed the road open, the route clear, the same calm blue line it always shows. We followed the blue line. A few kilometres later we hit the dead end exactly where the signs said it would be, had to reverse out, and found another way round that was not far off but was not the way we had planned either.

What stayed with me was not the wasted twenty minutes. It was that I watched a physical sign, in clear daylight, telling me one thing, and a screen telling me another, and some part of me trusted the screen more, right up until the tarmac itself ran out from underneath that trust. I got annoyed at myself afterwards, and at the app, which felt slightly unfair given how much data that company has presumably gathered from people like me just to get a road closure wrong. But underneath the irritation was something more uncomfortable. I had let a sign, the oldest and most basic form of information there is, lose an argument it should have won instantly, simply because the other source arrived on a screen and screens have quietly earned a kind of authority that paper and paint never did.

I think about this every time I watch someone, often someone sharp, someone I respect, read an AI generated summary of something important and nod along without checking a single underlying source. Not out of laziness exactly. Out of exhaustion, or out of the same quiet conditioning I caught myself in on that road. We are all carrying too much already, and verifying takes energy we have already spent on six other things before lunch. So we borrow trust instead of earning it ourselves, and we tell ourselves that borrowing trust is the same thing as having checked. It rarely is.

It feels, some days, like we are living by proxy. Someone, or something, is handing us a version of reality. A version shaped by filters we cannot see, assembled by processes nobody asked us to approve, and most of us nod along because questioning it costs more energy than we have left in the day. I do not think this is a story about a villain sitting somewhere deciding to deceive us. Nobody designed this outcome on purpose. It is a thousand small, reasonable decisions, made under real pressure, by people including myself, that add up to something none of us would have chosen if we had seen the whole shape of it from the start.

I do not have a clean way to close that thought, and I am not going to manufacture one. The discomfort is the point.

I can already hear the objection, because I have made it myself on other days. Every generation says this about whatever made the previous generation’s skill obsolete. People said it about calculators. People said it about spreadsheets replacing the army of clerks who once did long division by hand for a living. The work moved up a level, the argument goes, and the people doing it moved up with it, and panic about the lost skill always looks foolish a decade later once the new skill has settled into place.

I think that argument is right often enough that it deserves real weight, and I do not want to wave it away just because it is inconvenient for the essay I am writing. The calculator did not make mathematicians less capable. It freed them to work on harder problems than long division. I am genuinely open to the possibility that this is exactly that story again, just bigger and faster and more uncomfortable to live through while it is happening.

But I do not think every shift is the same shift just because the shape of the argument repeats. The calculator replaced a mechanical task. It did not replace the asking of the mathematical question itself, only the grinding arithmetic underneath it. What concerns me about where we are now is not that a tool got faster at the grinding part. It is that the asking itself, the formation of the question, the judgment about which question was worth asking in the first place, is increasingly something we hand over too. That is a different layer of the work than the one calculators ever touched. I am not certain that difference matters as much as I think it does. I am genuinely not certain. But I am not willing to assume it does not matter either, simply because the comforting version of the story has worked out fine before.

That uncertainty is, honestly, where I have landed for now. Not with an answer. With a sharper question, and an intention to keep asking it of myself before I let anyone else answer it for me.

I think that is, in itself, a kind of practice worth naming. Not refusing the tools. Not pretending the calculator argument is wrong just because it is uncomfortable. Just refusing to let the question close before I have actually sat inside it for a while. Most of the damage I have seen done by new technology over the years did not come from the technology itself. It came from how quickly we stopped asking what it was actually doing to us, because the asking itself felt like standing in the way of progress. I do not think slowing down here is standing in the way of anything. I think it is the last place left where the answer is still genuinely ours to give.

But I have been sitting with the original question long enough now that I think I have found one honest, partial answer to it. Not the whole thing. Just a thread of it.

When I think back over every version of myself in this story, the slip of paper on the service desk, the manager learning to delegate, the person typing an error message into AltaVista for the first time, none of them were actually valuable because of the answers they held. The answers changed constantly. AltaVista’s answers got replaced by Google’s. Google’s are getting replaced right now, by something faster and far more confident and not always right. If the answer was ever really the thing worth being, I would have nothing left, because none of my old answers have survived.

What survived is something underneath the answer.

It is the willingness to stand in front of someone who needs help and say, I do not know yet, give me a minute, while actually meaning it instead of performing it. That sentence costs something to say honestly. It is far easier to guess with conviction. I think the people who earned real trust from me over the years, in any role, were almost never the ones who had the most answers ready. They were the ones who were honest the moment they ran out of answers, and then went and found the missing piece anyway, in front of me, without pretending the gap had never existed.

It is the part of me that learned, on a packed call centre floor with phones dead and a manager shouting, which question to ask first and which one could wait. Nobody taught me that directly. It came from doing it badly a few times and feeling the cost of getting the order wrong. That instinct does not live in a model. A model will answer whichever question you give it with equal confidence regardless of whether it was the right one to ask first. The choosing of the question is still entirely ours, and I think it always will be, because choosing requires caring about the actual outcome in a way a prediction engine has no stake in.

It is the years spent listening to a team closely enough to know what feedback meant underneath the words they actually used. Someone tells you the workload is fine and you can hear, if you have spent enough time with them, that fine is doing a lot of quiet work in that sentence. None of that shows up in a transcript a model could summarise accurately. It shows up in tone, in timing, in the half second pause before someone answers. You only catch it if you were actually paying attention to the person and not just extracting the information you needed from them.

I think who you are without the answer is whoever was doing the noticing the whole time the answer was sitting in your hands. The judgment about which question actually mattered. The discomfort you were willing to sit inside instead of immediately resolving. The trust someone placed in you not because you always knew, but because you never pretended to know when you didn’t, and you went and found out anyway, in front of them, together.

That part, I do not think a model can take from us. Only we can give it away, and I think a fair number of us are giving it away right now without noticing, the same quiet way we once stopped walking over to a colleague’s desk because the search box was simply faster.

I am not writing this to tell you to put the tools down. I use them too, and I am not going to pretend that chapter of my own working life is over. I am writing it because I think the question underneath the convenience is worth asking out loud, on purpose, before the habit fully sets, rather than after.

I think that is part of why I wanted the sea that day, more than I realised while I was still driving toward it. Not for an answer. The sea has never once told me anything. I think I wanted to stand in front of something old enough and large enough that it had no opinion about automation, no answer to sell me, nothing metered, nothing priced by the token. Just the sound of it, doing the same thing it has always done, asking nothing of me in return.

I did not get that on the way home either, as it turned out. I got a blue line on a screen telling me a road was open that a painted sign, standing right there in front of me, was telling me was closed. I believed the line. I am still slightly unsettled by how easily I did. I do not think I came back from that drive with a conclusion. I think I came back with the same question the sea never answered, just pointed now at something closer to home, sitting on a dashboard instead of a horizon.

---

If you read this far and felt something land, the simplest thing I can offer is this. Every Tuesday I send one essay like this one, free, straight to your inbox, no catch attached to it. If that is useful to you, that is genuinely enough, and I mean that.

---

About the Author
Diamantino Almeida is a tech leader, coach, and writer reshaping how we think about leadership in a burnout-driven world. With over 20 years at the intersection of engineering, DevOps, and team culture, he helps humans lead consciously from the inside out. When he’s not challenging outdated norms, he’s plotting how to make work more human, one verb at a time.