Great article "Towards an understanding of technical debt". I really found this paragraph in point 2 an interesting way to look at things:
A little discussed and poorly understood design goal for code is disposability. Given change, what design patterns can we follow that allow us to quickly expunge incorrect behavior from our codebase? Interestingly it is a much more tractable metric for measuring as opposed to more popular criteria like “elegance”. (a post for another day)
Also this from point 4:
... We often describe this code with the suck-the-will-to-live quality as messy (spaghetti), unmaintainable, or amateurish. Often what we’re describing under the surface is fear and confusion. We don’t understand the code, and when we don’t understand things, as human, we tend to get scared, tired, and angry.
I had a project where this exactly described my experience. Enlightening.
Reading Contempt Culture and thinking about my own complicity in this kind of behaviour. I do think that i have (long?) grown out of this, but it is good to be reminded to take some time and reflect on how you interact with others.
Am in the midst of a discussion about this article here.
Really, what more need be said?
Played some Minecraft Dungeons with Ciara and Rory on the switch. That was quite fun. Oh and regular Minecraft too, with Conor as well. Everyone has a nicer house than me, even Ciara, who just played for the first time! I did build an underwater glass tunnel to an observation dome, which is pretty cool, so all is not lost.
Just noticing a couple sites which have "bars" to show you how far through the article you are? I just use the horizontal scrollbar on the browser itself, why duplicate that? Unless you have a shitty site with 100s of images and crap in the footer/header. In which case i have a whole host of different complaints.