The Late Night Reality

It’s late and I’m trying to finish these simple tasks. Maybe it’s the third attempt at providing a solid solution. But I’m tired—not from the task, not from the challenge. It’s just devastating to feel that you’re not enough. That something, someone will see something I didn’t know, something I couldn’t think of.

There’s nothing quite like when you solve a problem. That moment when you write the last words in the commit, sign off, and send the PR. CI passes and you think, “that was fun.” Until the next morning when the comments start piling up…

Understanding Value

I have to admit that my value feels low. I define value as something that your team and your boss want—something that makes everyone’s life easier and, ideally, is unique. It’s the knowledge acquired, the way of thinking, the solutions you provide, the new visions and ideas you bring, and your mentality as a human willing to serve.

Let’s step back for a moment…

The Responsibility of Being Last

When you’re the worst engineer on the team, you bear a large part of the responsibility. Likely you missed something. Or… no one taught you.

I find myself still learning, still being open-minded and observant. I’m still motivated and full of visions, ideas, and the right mentality. The knowledge is there—collective, though not always visible or instantly applicable.

What I’ve learned is that sometimes you need to slow down. Find a mentor. Or become one for someone else. Learn how to learn, and be consistent. The very first step: fix your communication. On every level.

Communication Beyond Words

I try to look beyond who says something to me or what they say. Instead, I try to understand where it’s coming from and what they actually need to communicate or ask. This helps me stay focused on tasks and not get caught up in the noise—the personality quirks that often obscure the message.

Some people need less but ask for more. Others want something important but don’t know how to express it. Usually, no one wants to get personal with you, so why should I provoke that situation? I’m here to grow—I’m just growing differently than others.

The Weight of It All

Being the worst on a team translates into stress, more mistakes, losing yourself. Losing faith and confidence.

But let’s say you find a way to manage all of this. You still need to transform the hours into passion, identify what you don’t know, and become technically adequate. There’s a realization—it’s almost a fact, spreading like a virus: all the negative feelings I just described stem from the simple truth that there’s something you don’t understand well enough, and everyone around you is struggling to transfer and explain it to you properly.

Another Problem to Solve

As an engineer, this is just another problem to solve. It doesn’t matter when the solution comes. Just be clear and honest with yourself about your goals and decisions. Be assured about where you want to go, what you want to achieve, with a clear plan and vision.

Be persistent.

And remember: being the worst engineer on a great team is still better than being the best engineer on a mediocre one.