Point It Out, Propose It 🛠️
Pointing out problems is easy and takes little effort. Understanding, proposing, validating and implementing is what actually creates value. On the difference between those who criticize and those who contribute.
Writing
Writing
Everything I write — in chronological order.
The Power of a Skill 🛠️
Everyone has opened an AI, asked for something, gotten a response, and moved on to the next task. The problem is that's only scratching the surface. Skills turn repetitive routines into recipes the AI can run on its own, from financial closing to investigating a bug in production.
Jumping on Grenades 💣
In war, when a grenade lands in the middle of the group, someone runs, someone just watches, and someone jumps on it. The same scene repeats every day in tech — and choosing to be the one who jumps is what accelerates a career the most.
The Next-Day Doctor 🩺
An exhausted doctor saves a patient at dawn. The next day another one, well rested, reads the chart and finds it all simple. The same scene plays out every day with legacy code. On judging decisions without knowing the context they were made in.
The Invisible Monster 👹
Deadlines that never close, deliveries that slip, endless problems. Almost always the fault isn't technical — it's everything we let slide. A conversation about the invisible monster that sabotages teams.
Spec-Driven Development — What we should have been doing all along, even without AI 🚀
Every time a new "buzzword" pops up in the development world, I notice a curious pattern: the community discovers, with an air of novelty, something that…
The programming language is not your first decision
If the first thing that crosses your mind when you receive a new project is "I'll use Go", "I'll use Node", or "I'll use Postgres" — pause for a second.…
Observability Is Not Just a Dashboard
When people talk about observability, the first thing that often comes to mind is a dashboard full of charts.
Chapter 16 – Consolidating Your Career in the Long Term
Reaching Staff, Principal, or Architect level is a rare achievement. But the question few ask is: “How do I stay relevant from here on out?”
Chapter 15 – Hybrid Career (IC + Leadership)
Reaching Staff level is a huge achievement, but it also brings a new question: “What is the next step? Continue on the technical path or become a manager?”
Chapter 14 – Is It Possible to Earn Well in Brazil?
One of the most common questions I get when talking about a technical career is: “Can you earn well in Brazil without becoming a manager or working abroad?”
Chapter 13 – Mentorship and Knowledge Multiplication
Reaching the Staff level means you are no longer just responsible for what you deliver, but also for what other people can deliver with your help.
Chapter 12 – Building Trust with Leaders and Peers
You can have advanced technical skills, communicate well, and even navigate conflict intelligently. But none of that holds up if the people around you don't…
Chapter 11 – Managing Conflict and Internal Politics
Many engineers believe that delivering good technical solutions is enough to grow. But anyone who has reached the Staff level knows: conflict and internal…
Chapter 10 – Communication for Influence
You have likely met someone who is technically brilliant but cannot explain their ideas. This is the type of professional who gets stuck at the Senior level.
Chapter 9 – Security, Resilience, and Performance
No matter how innovative, inexpensive, or scalable your system is: if it crashes at a critical moment or becomes an easy target for attacks, everything else…
Chapter 8 – FinOps and Efficiency
You can build the most sophisticated, resilient, and scalable architecture in the world. But if the cost is absurd, your company will inevitably question…
Chapter 7 – Distributed Architecture
Most applications start simple: one database, one API, and a front-end. It works fine at first — but as the product grows and complexity rises, one single…
Chapter 6 – System Design Beyond the Endpoint
When developers think about designing systems, many limit their vision to the API endpoint or the service they’re coding. But to operate at the Staff…
Chapter 5 – Building Your Personal Roadmap
So far, we’ve talked about the career map and the hidden side of promotions. But there’s one major mistake many engineers make: leaving their growth…
Chapter 4 – Behind the Scenes of Promotions
Many people believe promotions happen solely through technical merit or tenure.
Chapter 3 – The Leap to Staff: A Shift in Mindset
Reaching the Senior level is a milestone. You’ve mastered technologies, solved complex problems, and become a team reference. But there’s a trap: many…
Chapter 2 – What the Market Really Expects at Each Level
In Chapter 1, we learned that a tech career isn’t a simple ladder — it’s a journey where each step demands a new kind of impact. Now, let’s dive into a…
Chapter 1 – The Career Map in Technology
When someone enters the tech industry, they often imagine a simple and linear path: you start as an intern or junior, move to mid-level, then senior, and…
Path to Staff: The System Design Mindset
One of the biggest shifts in an engineering career happùens when moving from a Senior Engineer to a Staff/Principal Engineer. It’s not only about writing…