round green clock at 2:20

Writing software is a creative endeavor

A few books I’ve read and in fact the majority if not all of them (from decades old Mythical Man Month to Agile Estimation and Planning or more recent) all repeat the idea that the act of creation of software is a creative endeavor in the artistic sense of the word. My years in this domain for sure confirm it and furthermore, as with any “art” if it’s not done with pleasure, it’s not worth doing.

I wanted to write this post based on a discussion with former colleagues from a previous common employer which I shall not name who had the nerves of calling to the office a big batch of employees in full pandemic rise of COVID-19 only for the reason of a top-management visit, though the same employer had 2 recent infections in the ranks of other fellow colleagues. Of course, my friends were angry for being imposed to take a risk they do not want to take and because of the “slave” mentality of the employer.

Continue reading →

Continuous delivery of infrastructure as code using Go.CD and Ansible

I’m fond of the CI/CD movement, mostly because I can quickly see the value in automating the build and deployment pipeline and getting a quick feedback and if all tests pass, a good feeling of reliability of the service I’m deploying. A few years ago I would’ve used Go.CD for both CI and CD pipelines and I have yet to see a project that does not benefit from this ideology in some way or form.

The history of Go.CD starts as CruisteControl, probably the first CI software that was built in this industry, long before Jenkins became popular. Born in ThoughtWorks, backed by Folwer & friends, originally named Cruise in homage to the original CI tool, but quickly renamed to “Go” to avoid the confusion.

Continue reading →