Why "Why Not?" is a Critical Engineering Skill
A personal story about losing stability, taking a risk, and learning to operate without a clear roadmap
Prolog: I’m still thinking about a way to give more value for those who want to go further and get more learning, from the real world on Software Engineering and Technical Leadership. So far, I've got messages like this:
Having this relationship forged through the years following you, if the price were acceptable, I would pay for it.
— Senior Software Engineer
I’m still open for feedback. Please, pass by 👇🏻
Now, let’s get back to today’s issue.
Everything started with a message from Angel Suarez when we were finishing our Master's degree:
Marcos, what if we apply to this open possition at CERN together?
And I said
Yeah, don’t know… my english is really poor, you know?… don’t know if it’s worth it anyway… mmm… okeysh, let’s do it (what can I loose).
That was my Flashpoint, when everything started.
But let’s put a bit of context here.
“Stepping out of your comfort zone” is a phrase that has been worn out by overuse. It often sounds as if you aren’t constantly jumping into the void, you aren’t progressing.
But that’s not true in my experience, and I don’t believe in universal rules either.
Context matters, and a lot. What is a bold move for one person might be an irresponsible decision for another, depending on their current life stage.
However, there are moments when staying where you are is simply limiting your own growth. That’s where uncertainty comes in.
I know that could sound tough, but I always tell you I bring you real-life experiences, and real life is like that.
The context: From stability to chaos
About 13 years ago, my plan was linear: finish my degree in Oviedo, keep working there, and have a predictable life. It was a comfortable bubble.
But in 2013, the crisis hit hard in Spain. The company I was working with decided to let me go, and suddenly, that “stability” vanished. My first reaction was to look for the closest thing to what I already had: another job in Asturias, close to home, without overcomplicating my life.
That’s when Ángel, a good friend, sent me a link: a job opening at CERN.
“What am I even doing here?”
My tech stack at the time was PHP and MySQL. When I read “CERN,” my imposter syndrome kicked in immediately: “What am I going to do there? I build websites, not particle physics.”
Does it ring a bell to you?
But I asked myself a question that changed my perspective:
Why not?
Sometimes, that’s the only technical validation you need to apply for a role.
I passed the interviews and, three months later, I was landing in Geneva with two suitcases and a paper map in my hand. I was out of my comfort zone, and the feeling wasn’t one of “empowerment”; it was pure fear.
Reality at CERN: No instruction manual
I joined as a DevOps Software Engineer to work on the OpenStack infrastructure (the data center’s private cloud). But the real shock wasn’t technological; it was methodological.
In high-level environments, nobody sits next to you to tell you what to do step-by-step.
The mission: “Improve the UI of this system.”
The roadmap: It didn’t exist. You had to build it yourself.
That level of autonomy forces you to operate in a space where you can’t rely on routine. You either learn to navigate ambiguity, or you sink.
I’m not ashamed to admit that I didn’t know how to do that. Damn, I was thinking
Shit!, I want to come back home tomorrow!
But something changed inside of me. I managed to evolve. I managed to really understand why I was there, and the out-of-control situation helped my brain to figure it out.
What you gain when you let go of control
If you decide to take the leap (when your context allows it), two fundamental things happen for an engineer:
Your learning capacity multiplies out of necessity. You don’t learn because you want to add a checkmark to your CV; you learn because you have no other choice to get the job done and, of course, because that’s your goal!. You learn how to “learn fast,” which is the ultimate skill.
You ask for forgiveness instead of permission. When there’s no set path, waiting for 100% of the information is death by analysis paralysis. You start making decisions, failing fast, and correcting on the fly.
☝🏼 A necessary clarification
I don’t want to romanticize this. You don’t have to move abroad or work at CERN to “grow.”
These decisions only make sense if the timing is right. In my case, being laid off and having few strings attached created the perfect scenario. If I had different responsibilities or a different family situation, the risk might not have outweighed the benefit.
Stepping out of your comfort zone doesn’t have to be a radical change. It can be:
Leading a technical initiative for the first time.
Switching to a team where you don’t master the stack.
Giving a talk in front of people who know more than you do.
✨ Final thought
Real growth happens when you operate slightly above your level of certainty. Not in absolute chaos (which is just noise), and not in total comfort (which is stagnation).
The useful space is right in the middle, where you can still think clearly, but you can no longer rely solely on what you already know.
The next time an opportunity comes your way that gives you a bit of vertigo, before dismissing it, ask yourself:
Why not?
I’m pretty sure you have a similar case. I would love to hear from you. Reply to this email or drop a comment in Substack, I read them all!
Thanks for your support and feedback, I really appreciate it!
You’re the best! 🖖🏼
𝘐𝘧 𝘺𝘰𝘶 𝘦𝘯𝘫𝘰𝘺𝘦𝘥 𝘵𝘩𝘪𝘴 𝘱𝘰𝘴𝘵, 𝘵𝘩𝘦𝘯 𝘤𝘭𝘪𝘤𝘬 𝘵𝘩𝘦 💜. 𝘐𝘵 𝘩𝘦𝘭𝘱𝘴!
𝘐𝘧 𝘺𝘰𝘶 𝘬𝘯𝘰𝘸 𝘴𝘰𝘮𝘦𝘰𝘯𝘦 𝘦𝘭𝘴𝘦 𝘸𝘪𝘭𝘭 𝘣𝘦𝘯𝘦𝘧𝘪𝘵 𝘧𝘳𝘰𝘮 𝘵𝘩𝘪𝘴, ♻️ 𝘴𝘩𝘢𝘳𝘦 𝘵𝘩𝘪𝘴