
Two Weeks, 40 Commits, and an AI That Remembers My Preferences
Reading time: 12 minutes | Difficulty: Intermediate I didn't plan to write this post. But after two weeks of building across multiple projects with Claude Code, I looked at the git log and realized something interesting: the tool had gotten better at working with me — not because of a software update, but because it learned how I think. This isn't a review or a tutorial. It's a field report. What worked, what didn't, what I'd do differently, and a few tricks I haven't seen anyone talk about. 🔷 What Two Weeks of Real Work Looks Like Across my projects over a two-week sprint, Claude Code and I shipped roughly 40 commits. Security hardening. SEO fixes. Accessibility improvements. A comprehensive test suite overhaul. Automated blog cross-posting. Docker pipeline improvements. Translations. Refactoring. None of it was greenfield "build me a todo app" work. It was the messy, contextual stuff that breaks most AI tools — fixing hreflang tags on a bilingual site, debugging why Docker kept servi
Continue reading on Dev.to
Opens in a new tab




