I now know enough to be more dangerous.
Historically I’m a Windows developer (C/C++/C#). I’ve been using more and more Linux tooling and, day by day, the Linux learning is creeping in. A massive sprawling knowledge space, unfamiliar to me. But over and over again there are some basic bash scripting techniques I need, this is them.
Overview Recently, I have been thinking about my preference for structured logging (details on this in to-be-written entry). A trivial but significant aspect of this, is that once you have switched to structured logging, markers like INFO, DEBUG, ERROR,… don’t help. Simply grouping such a wide range of code paths into these categories is insufficient for any kind of analysis. What is an error? An error is a local failure scenario that you don’t currently understand - our continuous improvement process for error handling aims to move all these anomalies in the system from unknown to known.
Reasons to write code;
- Make money
- Save money
- Stay out of jail
- For fun
Whilst watching an episode of Francesc Campoy’s just for func series I noticed that there was a major feature of VS Code that was going unused. Multiple cursors. This is one of the biggest productivitiy features of modern text editors.
The code interview
The interviews I want to write about are specifically face-to-face code interviews. I have interviewed quite a few people over the years and too many of them seem to be going out of their way to fail. So these are my tips on how not to rule yourself out.
Making a change
When making a change to an existing piece of software I think there are broadly 2 options;
- Get in and out, change as little as possible
- Restructure the code to fit the new requirement
This is attempt N (where N is larger than I’d like) of actually setting up and adding content to a blog and or article based web site.