What kind of team member is Claude really? ⛳ A keen junior developer that wants to do exactly what it is asked. It knows a lot (everything?) about the language and has near-perfect recall of syntax—but still makes odd mistakes. For example, I asked it to update one user flow based on changes in another—and it did the reverse, overwriting the newer version with the old one. ⛳ A mid-level developer with more experience, but still lacking domain knowledge. You see this when crea

Don't debate, don't pontificate, don't procrastinate; just do! We all the scenario: the dev team is circling a gnarly problem and everyone is divided as to the best solution. We would breakout whiteboards and complete some sketchy diagrams with lines going everywhere, or paper an internal office for event sourcing sessions. What we didn't do was write code. Writing code felt like a commitment, whereas talking about it could be endless. I recently managed to procrastinate abou

I have done something I didn't think I would have to do. I thought, if I were pairing programming with Claude code, that I would be developing features so quickly that I would never need to implement 'feature flags' in the codebase. In reality, it was easy to code, but it was significantly harder to make secure. The 'Analyse your round' feature is an AI-powered interactive, question-and-answer session to help a golfer diagnose their biggest issue (for example, too many 3 putt

"Makes me think of taxis." Great if I was building an app for taxis, and not an app for golf. Feedback from users (beyond the above), indicated that the UI did not align to their expectations for a golf app: the colours were generic, there was too much yellow, and the buttons/clickable areas were unclear . Design is obviously something of a capability gap for me, so I needed a solution. Claude has helped me to deliver a cross-platform app that is distributed via the App Sto

Users, eh, got to love them. I created at app to explore agentic coding, help structure my golf hobby (obsession) and to learn more about React Native - see previous post . I then released it to the world and have received unsolicited feedback in return. Responding to feedback exposed capabilities gaps in my workflow. In my workflow, I had fallen into the oldest trap of all: Claude (mostly) amending the code I would review the code and suggest improvements (repeat step 1) Whe

I’ve been building a React Native app recently with Claude Code. Not because the world needs another golf app, but because I wanted one. Golf is my hobby and over the years I’ve read/learned a lot about how to play and practice better (despite evidence to the contrary on the course). The app is my way of coordinating all of my thinking into something structured. For example: * Score entry is designed to be ‘enter score and move on’ - focus on the present, not the past or proj