5 mistakes badass developers never do
Here is a one sentence summary of my previous post.
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...