You know that feeling. You walk into standup, everyone's talking about "the migration," someone says "just check the logs," another person laughs at a joke about Kubernetes, and you're standing there nodding like a bobble-head, understanding zero but performing "yes, this makes total sense to me too."
That was me. Three months into tech, surrounded by people who clearly knew what they were doing, while I was still googling what a "log" even meant in this context (spoiler: not the wood kind).
Here's what I've learned since — mostly by getting it wrong first.
What I tried first, that did not work
Nodding along. I nodded in so many meetings I basically qualified as furniture. Then someone asked me directly what I thought, and I had nothing, because I hadn't actually been listening — I'd been performing understanding. Lesson learned fast: nodding doesn't buy you time, it just delays the moment you get caught.
Using words I didn't fully own. I once said "let's make sure this is scalable" about a feature literally three people would ever use. A senior dev just looked at me. That look taught me more than any course.
Fixing my mess in silence. I broke something once and spent forty-five minutes quietly trying to undo it before anyone noticed, sweating like it was the last day of a deadline. Someone noticed anyway. It's always noticed. I might as well have said something at minute two.
Apologizing for existing. "Sorry, this is probably a stupid question, sorry to bother you" — I said some version of this weekly. Nobody needed the apology. They just needed the question.
What actually started working
Asking the real question, not the safe one. Instead of "I don't get this," I started saying exactly where I got stuck: "when I run this command, the error says module not found, but I've already installed it — here's my package.json." Suddenly people could actually help me, because I'd stopped hiding the specific place I was lost.
Saying "I don't know that word"out loud. The first time I asked "what's a log, actually, just plainly," I expected to be laughed at. Nobody laughed. Someone just explained it in one sentence and we moved on. Turns out most people have a list of things they also once didn't know and quietly figured out — asking just gets you there faster.
Talking about what I broke, immediately. "I broke the build, here's the fix" became my new default sentence. Nobody remembers the bug a week later. Everybody remembers whether you told them or they found out themselves.
**Building small, rough things instead of waiting to feel ready. **I stopped waiting until I "understood enough" and just built stuff — small, rough, sometimes embarrassing. Turns out a finished small project you can explain beats a half-finished big one you're still "planning."
Saying "I don't know, but I'll find out" instead of guessing. This became my favorite sentence in the whole room. Not knowing was never the problem. Guessing wrong and getting caught was.
The actual realization
Everyone in that room once sat exactly where I was sitting — lost, nodding, terrified someone would ask them something direct. They just stopped hiding it faster than I did.
You don't walk into the room already knowing what's happening. You walk in, admit you don't, ask the specific question, own the mess when you make one, and — slowly, without noticing exactly when — you become one of the people who knows what's happening. Somebody else is now the one nodding at the back, hoping nobody asks them anything.
Be kind to that person. You were just them.
Top comments (0)