It was a cold day in this first month of this new decade, a cold day full of coding. I was building some facade API…
Category: Development
New year, new project. Joining an existing project is hard. There are no shortcuts. But there are ways that the existing team can use to…
At one point or another during a project, we need to document the work we do. The more software we create, the more documentation we…
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…
Continuous delivery for free using Docker, CircleCI and Heroku
Posted in .NET Core, Building future-proof software, and Tutorials
Continuous what?
Continuous delivery. You may recall that in my previous post I announced that today’s entry would be revolving around continuous integration. And technically it can count as such since we will cover continuous integration along the next step. That next step is continuous delivery. If you are not familiar with these terms and the concepts behind them I will sum them up briefly.
Basically, continuous integration allows verifying that your codebase still builds and passes tests passing whenever you push changes. Add a trigger to deploy your code to production upon success and you pretty much have the idea around continuous delivery.