Topi Kettunen

Code reading has always been this activity that I’ve just done without really giving any thought to it. But despite this, now, when I look back at this habit, I see it is immensely beneficial. This habit caught my attention when I was reading Peter Seibel’s book Coders at Work, in which there is a section where Peter asks about code reading from his interviewees. It tended to be unanimous amongst his interviewees that code reading is very beneficial.

I’ve lately started to ponder the repercussions of this trend of extravagant architectural choices in the tech industry. Mostly these kinds of options seem to be prevalent in this current era of cloud computing. At least, I seem to stumble upon these regularly when I work with a wide variety of different distributed systems as a DevOps/SRE consultant. Great examples in this kind of trend are various Kubernetes setups in projects where you could easily manage to progress without it or some data infrastructure solution that feels like a sledgehammer for hitting a small nail.

I started to rekindle my, unfortunately, lost writing habit a couple of weeks ago. I set up Google Analytics for this page mainly due to its ease of use to see simple analytics. I was only interested in visitor count and possibly from what source my readers are coming. Google Analytics is a massive tool with massive amounts of data going into it. I tried to restrict this collection as much as possible so it suits my personal blog’s needs.