Search for a command to run...
I'm a seasoned Software Engineer with over half a decade of experience shaping the world of software development. My passion is anchored in writing code that is not just efficient, but also elegant and clean. An advocate for continuous improvement, I am forever on the hunt for the most cutting-edge developments in our dynamic industry.
No comments yet. Be the first to comment.
In the past few months, I've had a lot of discussions with fellow tech leaders but also friends who work in tech. All of them encounter different challenges in their daily work. However, some stuff stands out and I have this idea to create a story wi...
19th of July, Friday morning's events serve as a stark reminder of the critical importance of best practices and quality standards. CrowdStrike, a leading cybersecurity company valued at around $80B, had a huge outage because of a failed global softw...
I've genuinely tried to extract the best from SCRUM, be it trying Scrum by the book, or mixing it with a sprinkle of Kanban. It is just not proving to me that it does what it says it does... I know this topic is widely debated, and many other tech le...
Achieving operational excellence is a goal many organizations strive for. This pursuit often leads to the adoption of methodologies designed to streamline processes, boost efficiency, and enhance productivity. Among these, Continuous Delivery and LEA...
This will be fun! Let's start with something I experienced not too long ago. Imagine you're working on a crucial project with tight deadlines. You're heavily relying on an online collaboration tool. Suddenly, there's a server outage. But instead of c...
"Unit testing is an essential part of the software development process, and it can help ensure that your code is correct, reliable, and maintainable.β
Making private methods public just to enable unit testing is a big NO NO, because it couples tests to implementation and, ultimately, makes the tests fragile.
Donβt expose state that you would otherwise keep private for the sole purpose of unit testing. Your tests should interact with the system under test exactly the same way as the production code; they shouldnβt have any special privileges.
If you stub everything, you are testing a really small and simple and specific implementation detail. This will make your test fail almost instantly with a refactoring of a name or change in a serialisation method... Your tests will become unclear, brittle and less effective.
Donβt imply any specific implementation when writing tests. Verify the code from a black-box perspective
