Hello everybody, here we are. The day that I finally tackle CloudFormation. As far as I can remember I always told myself. Even though I…
Category: Building future-proof software
Future-proof software. For the longest time, I thought that future-proof software consisted in writing software so good you never need to change it. Over the years, I learned that it is actually software you should be able to change easily. Software that would adapt to future requirements while satisfying the current. Testing is a massive part of that. So is refactoring. Here are some blog posts around these topics.
If you are to embrace new requirements, you must design software so that you can refactor it. If you want to refactor your code, you need to have a way to test its current behaviour no matter how. For a web API, you may even go as far as using Postman to build a test suite.
And remember, whenever you build new production code. Write failing tests. Make the failing tests pass. Push to production. That way you never write unneeded code and if a refactoring is needed you have less to worry about. Yet you have enough to be confident while writing changes.
Back in September, I published a blog post on structuring a Go project in a fairly shallow way but deep enough for anyone to use…
A few weeks ago, I wrote a post on structuring a Golang app but wrote no tests whatsoever for it. All done on purpose, I…
Hacktoberfest 2020 will make you forget the pandemic
Posted in Building future-proof software, and Tech news
Developers Assemble! We are twelve days away from Hacktoberfest 2020. I will join the fest for the third consecutive time in this unholy year 2020.…
Setting up a WordPress development environment fast
Posted in Building future-proof software, and Tutorials
Ew PHP, right? High-fives all around. Except that for my generation, the first cool web app you’d create would be written in PHP, often coupled…