Software Architecture: The Bad Parts
My Thoughts
A practical walkthrough showing how seemingly reasonable architectural decisions can gradually turn a system into a big ball of mud. Learn about the Bad Parts of architectures.
You might also like
blog A Developer's AI Workflow: From Voice Dictation to Automated Reviews
The AI toolkit and workflow behind building three repositories, 347 commits, and a full-stack portfolio in under a month of part-time work — Claude Code, voice dictation, automated reviews, and more.
blog Building an efficient Content Pipeline with Claude Code: From PRs to Blog Drafts
I built a system that scans my GitHub PRs weekly, identifies content-worthy work, and generates blog drafts automatically. I call the pattern Quasi-Claw. I built a system to solve a problem most developers share: doing interesting work every week but never writing about it. The pattern — slash commands + LaunchAgents + CLI execution — turns Claude Code into a lightweight scheduled agent without any heavy framework or infrastructure. Here is how it works: 📅 The Trigger: Every Friday at 5pm, a macOS LaunchAgent triggers Claude Code. 🔍 The Scan: It scans my GitHub repos and scores PRs/commits for "content potential." 💬 The Summary: It sends me a Slack digest of the week's best stories. 🚀 The Execution: I run a single command to pick an idea, generate a full blog draft from the actual source code, and push it to my site’s API. The meta proof it works? This very post was identified and drafted by the system itself. #ClaudeCode #AI #BuildInPublic #Automation #SoftwareEngineering
blog How I Built a Full-Stack AI Portfolio for Under $1/Month
Four hosting services, three repositories, an AI chatbot, semantic search, and cross-device content sharing — practically free.