Who was it? It depends. If we were looking for a technically correct answer, it would be simply impossible to tell and someone who died long years later. But given his character, his stance, his acts and decisions and his legacy, it was Marcus Porcius Cato or if you prefer Cato the Younger.
I’m a strict person with a relatively high level of self-discipline. I’m strict with myself and with most of the others. Especially with those who I respect, with those who I consider more capable. I’ve recently realized that this might be a big mistake.
For one of the latest dojos in our department, we chose a relatively simple one to help new people get on board. We were working on the leap year kata in Randori style meaning that we were using only one computer - there were 9 of us.
We also applied some extra constraints, such as if after every three minutes our tests were not green (except for the red phase when we had to write a failing test), we had to wipe out our changes (git reset --hard).
In an era when so many people want to have the next big shot when everyone wants to come out with the next big thing and suddenly find themselves at the top, this book, The Compound Effect by Darren Hardy has a very important message. Success comes from small actions, small but consistent and repeated actions.
We were going on holidays recently and we were going far away. We were travelling to Vietnam. The last time before my daughter would go pre-school and my son would start walking. In other terms, the last time before our schedule would become more fixed and the last time we can buy an infant ticket to my son and saving some money.
With one of my colleagues, we’ve been working a lot to create and foster a culture of learning, an environment where constant self-improvement and knowledge sharing is highly valued. Let’s say that we are part-time developer advocates. We’ve achieved some of our goals, but there is still a long way ahead of us. The “us” applies both to the developers and the management.
Code Ahead, what shall I call you? You are a novel. A fiction. Yet according to you, you’re semi-autobiographical. You are a rather exact picture of how things go in software development. Yet you’re also a manifesto of how things should go instead. You give lots of pieces of advice on “programming, debugging, releasing, testing, organizing, teamwork and management issues”.