Author: Edvaldo Freitas
-
What’s the real impact of AI in Software Development
AI in software development is becoming the new normal for engineering teams. It’s built into IDEs, pops up in pull requests, reviews code, and even writes tests. But between all the hype and the real world, there’s still one question bothering a lot of people: what’s actually changing in the day-to-day of someone who writes…
-
Feedback in Pull Requests: What High-Performing Teams Do Differently
Everyone talks about how important the code review process is for quality. But few people go deep into what really matters — how to give great feedback in a pull request. And more than that: how to receive that feedback without freezing, taking it personally, or turning every PR into an endless debate. If you…
-
Software Metrics: A Guide for Engineering Leaders
If you lead an engineering team, you already know: picking the right metrics can be the difference between well-informed decisions and shots in the dark. In this article, we go straight to the point: which software metrics actually help leaders guide their teams with clarity and focus. No magic formulas. Not every software metrics deserves…
-
How to build a strong code review culture
Code review isn’t just about catching bugs. It’s not just about keeping code quality high. A good code review culture is about how a team learns together. How it grows, improves collective quality, and avoids knowledge being stuck with just a few people. If you’re leading an engineering team, you need to see this not…
-
How engineering teams want to use AI in software development
With all the buzz around AI in software development, it’s easy to get lost in the hype. But what do engineering teams actually expect from these tools? The truth is, at the core, every tech team wants the same thing: fewer boring tasks, more time to think. They don’t want AI to write an entire…
-
Pair Programming: when it’s worth it (and when it just slows everything down)
Pair programming—some love it, some hate it. For certain teams, it’s a game-changer for code quality and collaboration. For others, it’s a massive waste of time and energy. But like many software engineering practices, the answer to “Should we adopt it?” depends on context. In this article, we’ll break down the real benefits and challenges…
-
How to plan your engineering team’s capacity
f you lead an engineering team, you know that planning engineering capacity is no easy task. As your team grows, it becomes increasingly difficult to ensure on-time deliveries, maintain high-quality standards, and avoid the dreaded burnout. But here’s the thing: planning capacity the right way can simplify your life significantly. In this article, I’ll help…
-
Developer Experience: 6 Warning Signs
Developer Experience (DX) is at the core of any company that truly values its engineering teams. When the developer experience flows smoothly, the team becomes more productive, and processes become more agile. But when obstacles start popping up, everything gets complicated: rework, frustration, and a drop in productivity. If you want to enhance your team’s…
-
What to Prioritize in a Code Review
If you’ve ever been part of a code review, you know the experience can be either great or incredibly frustrating. In an ideal scenario, it’s a process that improves code quality, accelerates team learning, and ensures the software evolves sustainably. But when handled poorly, it can turn into a cycle of irrelevant feedback, unnecessary discussions,…
