Hey, look at that — I’m writing a blog post again! Seriously, apologies for the lull, but, hey, life happens.
Enough of that, though. Let’s dive into some realio-trulio, software related content.
I Read an Interesting (Horrifying) Tale This Morning
Lately, instead of starting my day blearily looking at my phone and the emails that have trickled in while I slept, I’ve been starting each day with unstructured reading and chatting. I randomly read my feed, talk to people on Slack, watch a Youtube video, or take some research flight of fancy.
Anything goes as long as it’s:
- Not completely mindless
- Not directly related to work I’ll do
I can’t recommend this practice enough, especially for the self-employed set. It stimulates creativity and sort of gets all of the things that normally distract me out of the way.
But I digress. The real point of this mini-anecdote is to say that I read a blog post from Uncle Bob Martin this morning. It’s a compelling read, as his posts generally are, and it talks about the recent Boeing crashes.
Here’s something that jumped out at me, though, somewhat oblique to the narrative, and relatively mundane in an otherwise pretty grim tale.
Rather, programmers must [have] intimate knowledge of the domain they are programming in. If you are writing code for aviation, you’d better know a lot about the culture, disciplines, and practices of aviation.
And then, this, at the end:
We have to know the business domains we are coding for.