Categories
weeknotes

Weeknotes: 35/34

  • August is the last month of my employer’s financial year, which means preparing for annual appraisals just as everyone is using up their leave – and this is on top of client work. While I’m enjoying being busy, it’s also been tiring.
  • We finished off our internal Summer of Q, where about 40 of us explored agentic AIs for coding. It’s one of several things I need to write up before I forget about them. I love working with agentic AI, but doing it effectively will take some more work.
  • I continue to think about Sean Goedecke’s essays on value, alongside his one on Pure and Impure Software Engineering. I’m mentioning Goedecke in most of my weeknotes recently. I have been rereading some of his pieces and want to put them into practise when I start a new role in September.
  • My new role involves React, so it’s time to get to grips with that properly.

Links

Categories
weeknotes

Weeknotes: 2025-33 to 30

  • It’s been a few weeks since my last weeknotes. I had a restful holiday in Wales and a lot of work things to catch up on.
  • I’ve been thinking a lot about Sean Godecke’s essays on the role of a programmer in the current economy, and the need to provide demonstrable value – particularly for seniors and managers. This is shaping my approach to my work.
  • I wrote a post about how The Joel Test turned 25 this month, looking at its historical importance and pondering what a modern Joel test might include.
  • In another flight of nostalgia I looked up Brad Fitzpatrick and Lisa Philip’s notes on scaling Livejournal, which were a useful reference for scaling Flirtomatic many years ago.
  • I continued my experiments with Amazon Q and learned a lot. I should have those written up by the end of the month.

Links

  • The 2025 Stack Overflow Developer Survey has been published, although it may be a few weeks before I get around to reading this properly.
  • Another great piece from Charity Majors was In Praise of ‘NormalEngineers, where she talks about the importance of teams rather than individual developers, and how systems must be easy to use: “The best engineering orgs are the ones where normal engineers can do great work”
  • Sean Goedecke’s What’s Going to Happen to Junior Engineers was a good exploration of the potential long-term meaning of the fall in junior tech positions.
  • The conclusions of Anthropic’s Project Vend feel quite speculative, but it raises some interesting questions: “we think this experiment suggests that AI middle-managers are plausibly on the horizon… the AI won’t have to be perfect to be adopted; it will just have to be competitive with human performance at a lower cost in some cases… we don’t know if AI middle managers would actually replace many existing jobs or instead spawn a new category of businesses”.
  • Welcoming the Next Generation of Programmers argues that vibe coders are programmers and it’s important to onboard and welcome them to the existing developer communities.
  • Christina Wodtke posted on linkedin about how a lot of Gen-X programmers have the same passion for GenAI as for the early web – in a way that didn’t happen with blockchain or VR (via Simon Willison)

Books

Tidy First by Kent Beck

I read Kent Beck’s Tidy First? while away – some thought-provoking ideas, but they rely on being able to produce and merge changes easily. Again, I need to find time to write up my notes.

Categories
programming programming-life

The Joel Test is 25

On Saturday, the Joel Test turned 25 years old. This is a 12-question checklist to assess the quality of a software team. Many of its points are now universal, but it got me thinking about what might be on a modern Joel test.

The test was written by Joel Spolsky, then of Fog Creek Software, but better known now for Stack Overflow. According to Spolsky, 10-or-less out of 12 suggested serious problems. The Joel Test provided me with a useful set of questions to ask potential employers and helped me avoid some dodgy companies.

Some of the items on the test show how far programming has come in the last quarter century. Back then, not every team used source control, regular builds, or bug databases. A few other things are still not as common as they should be – not every company asks developers to write code during an interview.

What would I put on a modern Joel test? I would add active monitoring of production; early and regular review of software by product owners; documented onboarding processes for new hires.

Even though we’re in the early days of learning about GenAI, I think it’s already essential for teams and companies to provide training and hands-on experience with the new tools. Whether these produce a 10% or a 10x increase in developer output, they will become essential.

What other things are essential for a successful software development team?