Architecture

Last time I argued that you can’t design your way to a good abstraction. You have to earn it through repetition. Here’s what that actually looked like. I had six Python projects, each containing its own version of the same four files: A provider abstraction for talking to LLMs CLI argument helpers Obsidian utilities for reading and writing notes A testing module for stubbing out model calls I knew that I wasn’t sharing code between the tools and that each would have similar needs. But it wasn’t my priority to fix, so I let it happen. And the code accumulated, one project at a time, each one re-creating a variation on the same logic. Like a lazy developer, copy-pasting code from another repository and tweaking it to fit. ...

Ever find yourself writing the same code in a different repo? I have. What did you do about it? Maybe your first reaction is to reach for an existing library to do the work for you? Or perhaps you start thinking about the DRY principle and how you need to start optimizing and combining your code. I’m up to 16 different repositories, each containing a tool that I’ve vibe-coded with some help from Claude Code and/or Gemini. Things like: ...

Today I joined the AWS Card Clash: Gen AI Battles | S1 E1 | Model Access Showdown on LinkedIn. This session demoed the AWS Card Clash learning game available on AWS SkillBuilder. The session was hosted by Curtis Morton, Jason Cuddy, and Brittany Wolfrom. AWS Card Clash is a fun and engaging card game that pits two players against each other to complete architecture diagrams. Some of the things that I liked about this as a learning activity are: ...