Methodologies Suck Formally structuring what you do is great, because it helps anyone somewhat removed from the project quickly understand where you are. It also helps establish some sense of repeatability and an opportunity to continuously improve. But don’t get caught up in the methodology madness.
The engineer that wasnt there Turns out that the term software engineer, was never really meant to be adopted by coders. It was used as a challenge to developers at a NATO conference in 1968 to be more structured and methodical.
Are You Sitting Comfortably A brief introduction to the concepts of narratology, and why they can help you do better presentations.
Seeing the Spoon A kick-off article for the site in general, or why I decided to get a few things of my chest
Here’s the consolidated version of the essay: Software Complexity and Why Being Intentional Matters In software development, we’ve all felt that sinking feeling upon opening a codebase and thinking “WTF is this code doing?” This visceral reaction to unfamiliar, disorganised and often just plain badly designed software isn’t just about aesthetics—it’s about