Skills, Plugins, and MCP Oh My!
Looking for even more Claude Code tips? Never fear, I definitely have more. This is where things get interesting...
Looking for even more Claude Code tips? Never fear, I definitely have more. This is where things get interesting...
Ok. Enough waxing poetic about AI. Here's how I use Claude Code to build software.
Tools change. Models improve. Features ship faster than you can even imagine. But after months of experimenting with different AI tools and workflows, I noticed certain patterns kept appearing. Strategies and principles that yielded good results regardless of which shiny new thing I was using. And I found myself coming back to them time and time again.
AI is taking the world by storm, and no place more heavily than the software engineering industry. Agents are writing non-trivial percentages of production code bases to systems you are using every day now. What was once a scarce resource, code, is now cheaper than it's ever been. What it means to be a software engineer is changing fast, and those that don't adapt risk being left behind. So, in respect to adopting AI, as my great-grandmother would say, it's time to shit or get off the pot.
Change is inevitable. Technology advances, new tools emerge, productivity increases. The wheel keeps turning. The emergence of LLMs has had a Big Bang level impact on many industries, suddenly and almost violently changing what we know and how we think about everyday aspects of our life seemingly overnight. Love it or hate it, one thing's for certain. We're witnessing the evolution of software engineering in real time. And it's time to stop pretending like we aren't.