We all know how to write a unit test for our application logic or an integration test to cover a larger piece of our software. Yet software today seems to be more fragile than ever.
But there are a few extra ways to increase the quality of your code base and prevent some easy to catch bugs (which still cost time and money to fix), and lower the amount of frustrations in/between your dev teams. Easily pinpointing which of the 20 microservices you depend on is acting up, will be the icing on our high quality cake.
While the samples are technology-specific, the practices can be applied to most common used technologies.
Consultant during the day, hobbyist at night.
Bart is an independent consultant, and technical architect at AE focusing on the Microsoft technology stack, covering anything between cloud and backend services to Windows and mobile. He’s always open for a new challenge and eager to learn.
Bart keeps a personal blog at http://www.bartlannoeye.com/blog/ on which he describes his discoveries and findings on the problems he encounters during his daily tasks.