How can we exploit short time slots here and there to perform large scale refactoring?
Incremental Software Development Strategies for Large Scale Refactoring #1 : Constant Merciless Refactoring
Here’s everything you need to find the time for constant merciless refactoring … without asking for the permission!
In the end, incremental software development techniques are almost always the safest way to refactor. Here is why.
There are some simple attitude principles that badass developers follow to gain the business people trust.
Here is a one sentence summary of my previous post.
My last post was about the challenge for dev teams to get sponsorship for large scale refactorings. I listed two main reasons :
Whenever I present or suggest a good practice to dev teams, I often get the same remark. Here is how it goes :
I had the chance to attend Devoxx France this year in Paris. Here is the most important lesson I learned :
My current job at work is technical coach. I’m available for teams that need help to adopt incremental coding practices.
In the previous 7 articles of this series, I’ve tried my best get rid of mocks. I’m pretty sure that using these techniques will get you a long way out of mo...
Last week’s post was about how hexagonal architecture results in fast, mock-free tests around your core domain. Unfortunately, that does not remove all mocks...
As I’ve written in my last few posts, we can get a long way to avoid mocks with small scale coding best practices. Unfortunately, when systems reach a certai...
Custom assertions are a handy compromise alternative to mocks when we don’t have the time to refactor to a functional style.
We are sometimes tempted to use mocks to shortcut test data initialization. Unfortunately, excessive mocking makes tests difficult to maintain. As Uncle Bob ...
In my previous post I explained how Immutable Value Objects help us to avoid mocks. In this post, I’ll illustrate this in practice with real code.
Excessive use of mocks makes tests very painful to maintain. If we stick painful mocks for too long, we’ll end up abandoning unit testing. Eventually, the sy...