I received two comments that stuck with me:
"You can't work that fast… what will the other developers think?"
And later:
"Don't pick fights with everything. That's what managers are for, you do what they say and move on."
At that moment, I was genuinely shocked. Over time, I realized the problem wasn't working fast, taking initiative, or wanting to improve processes.
The problem was being in an environment where questioning technical decisions, pointing out real issues, or proposing improvements was seen as an inconvenience rather than something positive.
🤔 The Real Problem Isn't Your Initiative
Many times the problems don't originate from the development team itself, but from external decisions, poorly defined processes, or architectures that clearly would generate technical debt.
But pointing it out seemed to be interpreted as "creating conflict" instead of trying to prevent future problems.
And I think many of us developers have experienced something similar:
- Wanting to do things right
- Trying to think beyond "just execute"
- Proposing improvements
- Taking care of technical quality
- Or avoiding mediocre solutions…
…and ending up feeling like that bothers people more than it helps.
👌 The Most Important Lesson I Learned
Over time, I understood something fundamental:
Not all environments value initiative in the same way.
There are teams where curiosity, proactivity, and critical thinking are rewarded.
And others where the most comfortable thing is not to question anything and simply follow the marked path.
Looking back, that experience helped me tremendously understand the kind of culture and teams I really want to be part of.
🙌 The Best Teams Don't Avoid Difficult Conversations
Because ultimately, the best teams I've worked with aren't those that avoid difficult conversations.
They're the ones that allow ideas to be discussed in order to build better solutions.
Teams where:
- ✅ Questioning is welcome, not a nuisance
- ✅ Problems are addressed, not ignored
- ✅ Continuous improvement is part of the culture
- ✅ Critical thinking is a value, not a risk
- ✅ Technical truth is sought, not comfort
💭 A Final Thought
If you're in a place where having initiative looks bad, where proposing improvements creates discomfort, or where you're simply expected to execute without thinking…
You probably shouldn't be there.
Because the price of staying silent is much higher than speaking up.
And the best teams already know that.