Programming
-

Seeing the bottlenecks in the software factory
→: Seeing the bottlenecks in the software factoryThe baseline of the software factory is output. Ours runs at about 2 PRs an hour, which adds up to daily releases of around 50 PRs (Mondays are often bigger, given it also works weekends). This is nice, but over the past couple of months I’ve been taking that output as a given, and trying…
-

The role of engineers in the software factory
→: The role of engineers in the software factoryThe other week, I found a menu button in the wrong place on mobile. Floating around the middle of the page when it should have been anchored to the side. Two things went through my head. First, the disappointment of finding a bug on the weekend. Second, we had things in place to prevent exactly…
-

Attempting to reverse engineer code review
→: Attempting to reverse engineer code reviewI keep hearing complaints about code review. About volume, about quality, about trying to take responsibility for code produced by colleagues who have abdicated their responsibility for thinking and are uncritically hitting enter. But how much of that is just grumpiness? Frustration? “AI slop” is the new “I didn’t like it.” Code review was always…
-

Is the software factory working?
→: Is the software factory working?When we replatformed Twill, we built a software factory: agents write most of the code, a merge queue lands it, CI decides what gets through. Which means there’s a lot of activity, and every release I cut (several a week) includes a list of changes. But I need to know if the factory is working.…
-

Good Architecture Is a Function of Time
→: Good Architecture Is a Function of TimeEngineers, we use a lot of words to talk about architecture, but at a fundamental level, I think architecture is about making good decisions easier, on a timeframe you can reason about. → Small startups can’t reason about a long timeframe, so architecture has limited ROI.→ Banks have requirements around audit trails and – for…
-

Maturing our development process as an AI-first 2 person team
→: Maturing our development process as an AI-first 2 person teamWe’re doing a big release this week for DRI Your Career. Mostly bug fixes and reliability work nobody will notice, but the two things worth mentioning: We’ve come a long way since it was just Jean and “Claude the intern”, but mostly very iteratively. We’d come to a point where it seemed worth rethinking. We…
-

WordPress + Claude – a new look for cate.blog
→: WordPress + Claude – a new look for cate.blogIf you’re reading this on cate.blog, things look different. I’m pleased with how it came out. Getting there was more difficult than I expected. I came into this confident. I used to work on WordPress (admittedly, the mobile apps – but I did the support rotations and lived in P2 like everyone else). I have…
-

High Throughput, Low Completion
→: High Throughput, Low CompletionI have never been someone who organises things. I have a great memory and a high tolerance for ambiguity, and I evolved to match the era of the internet where searching things by keyword was sufficient. I documented, extensively. But I did not really organize. Not myself, nor – despite my job – other people.…
-

A Season of Learning
→: A Season of LearningThere’s a concept in computer science called explore vs. exploit. Exploitation means using what you know to get reliable returns; exploration means trying new things at the cost of those returns. Most algorithms skew too hard toward exploit. Humans have also been known to do this – including me. The known path is comfortable. My…