The Agile Echo
Learn Agile Practices Blog
When it comes to growth in our careers, the best outcomes come from having a deliberate plan. In 2025, I’ve decided to take a strategic, question-first approach to my learning. Instead of chasing trends or trying to consume as much content as possible, I’ve outlined the core questions I’m currently wrestling with in this stage of my career.
Latest articles
Best Practices for Test Doubles
A comprehensive guide on test doubles and how they can help you become a better software engineer. Explore the best practices for using test doubles effectively to enhance your software engineering techniques.
How to Become a Better Software Engineer
Becoming a proficient software engineer isn't just about writing code—it's about mastering a wide range of skills and adopting the right mindset to excel in your career. In this blog post, we'll explore 10 practical tips to help you become a better software engineer.
More articles
What if We do Ensemble Programming all the time? 🧑🏻💻👩🏽💻👨🏻💻👨🏼💻
Let's have a look at the fascinating subject of Ensemble Programming, including its ideas, advantages, and possible impact on software development processes. Ensemble Programming has the potential to transform the way we develop software by encouraging collaboration and improving code quality. So make sure to be ready to read this with an open mind while I tell you the potential benefits of adopting Ensemble Programming as a mainstream practice in the software business.
London vs Chicago: The two ways of TDD 🔀
We go back to talk about Test-Driven Development (TDD) today, with a little twist—we're exploring the two main different approaches of the two iconic TDD schools: London and Chicago. Each TDD school brings its unique flavor to the table, offering a different perspective on how to approach software testing and development with TDD. In this article, we'll describe the two approaches and compare them.
eXtreme Programming for Remote teams
I’m a big advocate of eXtreme Programming, as most of you already know: since the first time I read “eXtreme Programming: Explained”, this methodology has become part of my daily job as a Software Developer and it’s the core of what I typically bring as suggestion when I’m technical coaching. Then, remote work became a habit and it seems that the direction where this type of work is going is diverging from the values and principles of XP itself; most people think that XP (and Agile) practices are not compatible with remote - but is this actually the truth?
Are we sure async Daily Stand-ups are a good idea? 🤔
This practice is one of the most used (and abused) among all the Agile practices, and it has been misinterpreted and misused for a lot of years (the usual example is that it becomes an update meeting) - and now that working remotely has become very common, a lot of tools that implement an “async” stand-up are used by a lot of teams, adding another misuse of the practice.
CQRS pattern: advantages of Command and Queries
I think CQRS deserves its autonomous role in Software Development and should be discussed more because it is a powerful technique to organize our software and keep it maintainable. This is what I want to do with this article: describe what the CQRS pattern is about, with some practical examples and usages, and especially highlighting its advantages on a business application and why it makes total sense to apply it on its own, no need for ES.