No, I did not get a stroke while writing this headline, and yes you read that right. In today’s post, I shall write about development-driven…
Once upon this morning This morning, for the first time in a while, I cycled to work. It had been a few weeks since the…
A code refactoring how-to: Killing unworthy software
Posted in Building future-proof software, Java, and Tutorials
Welcome back to the future-proof series! Today I thought I would present to you a case very close to a code refactoring I made recently…
My Musketeers for DotNet Test driven development
Posted in Building future-proof software, and Productivity
Test, four letters, one meaning and for some people a struggle. Getting people around you to write tests is easy only when everyone already agrees with you. As often, there are instances where some people show resistance to writing tests. Here
D: I don’t have time to write tests.
A: I don’t need to test this.
B: I can’t write a test for this.
Simple continuous integration with Appveyor and Newman
Posted in Building future-proof software, Productivity, and Tutorials
Last month, I posted about Postman enabling you to test your APIs with little effort so that you can build future-proof software. Here we are going to cover setting up continuous integration for a simple project by using Newman to run your Postman collections. You may have heard about continuous integration in the past. Most commonly, continuous integration will build software from one’s changes before or after merging them