This blog isn’t about some perfectly balanced programming practice. I don’t think that exists. Different situations call for a different emphasis. I’m going to talking about programming, how I do it and why. That might be the right way for you or it might not. Think about what you want to achieve and what is needed for that. There are many software development rules and guidelines out there. They can be great, they can be terrible, they can even be both.
I graduated university in the late 1990s and have been working with software ever since. Mostly of that time has been spent in small teams, as part of small to medium sized companies. I’ve written a lot of new code but also worked with a lot of existing code. This often involves revising and improving code to make it more consistent, smaller and more understandable. More recently I’ve spent time thinking how to organise the processes as well as the code itself.
My primary development languages have been C++ and C# with a few others mixed in. Most recently it’s been C++ with a bit of python for scripting. For the moment any examples are likely to use C++ but the principals will probably apply to other languages.
The schedule has changed a bit depending on available time. Initially it was a couple of times a week, normally Tuesday and Thursday, for the first few months. Then once a week on Tuesday for the middle of the year. Currently there’s not a regular schedule, it depends what else is going on and what ideas I come across. The intended focus the blog has shifted from the beginning but encourages people to think about not just what they do but why.