Writing
Everything I write — in chronological order.
Through October, AI showed up in one in five announced layoffs in the US, nearly tied with "market conditions." Add up every reason tied to a weak economy and one analysis gets to 66%, so anyone worried about their job in 2027 should watch both risks.
Nobody misses doing long division by hand, and a lot of what AI is taking off your plate can die in peace. The problem is the other part: the one you'll only notice you lost the day the agent gets it wrong.
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.
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.
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.
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.
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.
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…
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.…
When people talk about observability, the first thing that often comes to mind is a dashboard full of charts.
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?”
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?”
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?”
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.
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…
Many engineers believe that delivering good technical solutions is enough to grow. But anyone who has reached the Staff level knows: conflict and internal…
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.
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…
You can build the most sophisticated, resilient, and scalable architecture in the world. But if the cost is absurd, your company will inevitably question…
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…
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…
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…
Many people believe promotions happen solely through technical merit or tenure.
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…
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…
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…
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…