31 Days of Vibe Coding

31daysofvibecoding.com · English

Learn to ship production features faster with AI. Real tactics from building collectyourcards.com - no hype, no theory, just what actually works.

atom

Open the feed

https://31daysofvibecoding.com/feed.xml

Last post: Mar 6, 2026
Posts in 24 h · 7 days · 30 days: 0 · 0 · 0
Our last check: Answering
Served from: United States
Site title: Vibe Coding with Jeff Blankenburg
Text score: 6,774
Format: atom

Posts

What our queue read from this feed. Open one to read it here, or go to the site that published it.

Walking With Claude
Mar 6, 2026 · original
I’ve noticed that since I started my journey into AI-driven software development, I’ve almost entirely stopped going for long walks for exercise. Some of this was the cold weather, but most of it was the dopamine. “Just one more feature.” I always wanted to stay close to my machine, because it would regularly ask me for permissions, or a clarifying question, and I didn’t want to waste the time it might wait for. I’ve been telling myself for months that I should figure out how to configure my machine to allow remote access from my phone. That way, I could kick off new features from the couch, from the car, or even on a walk. So I spent some time last weekend doing some research to see how others had approached this problem. And that’s when I discovered Claude’s “/remote-control” feature that had literally only been released 4 days earlier. A video makes a much better illustration of how t
My First Big Test
Feb 27, 2026 · original
I’ve been vibe coding apps for the last 10 months almost daily, at least according to my GitHub activity. But May 1 will be my first big test. In addition to everything else, I also run a software development conference called Stir Trek here in Columbus, OH. This will be the 17th year for the event, and the first time we will have an app for attendees. For a team of 10 volunteers, building a cross-platform app with all of the data and capabilities necessary to serve 1,600+ attendees was just too much to take on. Until now. This weekend, I’ll be building a complete app, from start to finish, that provides the following capabilities: Full schedule view, with “build your schedule” capability. Speaker photos, names, and bios linked to their talks. Sponsor listings, with links to their websites. Dynamic polling throughout the event. Session review capabilities, for speaker feedback. Venue map
Building Bro Madness
Feb 20, 2026 · original
Last week, I talked about how quickly I was able to create a scoring app for a card game. I had a similar experience this week. Next month in the United States, the college basketball tournament starts. The best 64 teams play 63 games to determine a champion. A standard bracket for the tournament The most fun part of this tournament for me is the first weekend of games. Thursday: 16 games. Friday: 16 games. Saturday: 8 games. Sunday: 8 games. This eliminates 75% of the teams from the tournament. Each year, 25 of my friends rent a giant cabin, and spend the weekend watching those 48 weekend games. Lots of wagers and games take place as a result, and those games have all traditionally been entered and managed on paper. It felt like this was an opportunity to use AI to build an app that would make all of these games much simpler to administer and score, but also a way to have everyone conne
Card Games
Feb 13, 2026 · original
I spent the weekend with some old friends and all of our children in a tradition we call “No Moms Weekend.” It’s 7 dads, and 15 kids of varying ages all doing wintery outdoor activities like hiking, making campfires, and playing lots of games. Moms have to stay home and suffer through the peace and quiet of an empty house. One of our favorite games to play is called Backalley. It’s a trick-taking card game played with a standard 52-card deck. It always involves 5 players, and it’s played in 20 rounds. The first round every player gets 10 cards, then 9, then 8, until you get down to 1. Then you repeat the entire process back up to 10. There are some important data points to record for each round as we play: How many tricks did each player think they would win this round (bids)? How many total bids were made? How many tricks did each player actually win? What was the trump suit? What is th
Welcome to the Blog
Feb 6, 2026 · original
For a 31-day series, I had to write much of the content ahead of time. Most of it was completed in November or December 2025. The world of artificial intelligence is moving so quickly, it almost feels like the moment you post something, it’s out of date. This series still stands on its own. I tried not to lean too heavily on any specific agent or technology to keep the perspectives timeless. Audio Versions of the Series My friend Sean Kelly decided to do a little vibe coding of his own (a lot of vibe coding, actually), and created audio versions of this entire series. You can read about his experience figuring out how to create audio files from my articles here . I’ve also added a link to each audio file at the top of each article. The 31 Days series taught you the fundamentals of AI-assisted development. Now this blog continues the conversation with fresh content every Friday. What to E
Day 31: Your Personal Vibe Coding Playbook
Jan 31, 2026 · original
You made it. Thirty-one days of tactics, prompts, and practices. That’s a lot. Too much to use all at once. Too much to remember without a system. Today we build your personal playbook. Not everything from this series. Just what works for you. A reference you’ll actually use. A foundation you’ll build on. What Goes in Your Playbook Your playbook is personal. Mine has: CLAUDE.md - My agent configuration common-ai-mistakes.md - Patterns AI gets wrong in my projects prompts/ - Templates for common tasks checklists/ - Pre-commit, pre-deploy, review checklists runbooks/ - What to do when things break Yours might be different. That’s the point. Take what works, leave what doesn’t. Building Your CLAUDE.md Your agent configuration is the foundation. Here’s a template: # Project Configuration ## Tech Stack - Language: [TypeScript/Python/etc.] - Framework: [React/Express/Django/etc.] - Database: [
Day 30: Managing Technical Debt When Shipping Fast
Jan 30, 2026 · original
The code worked. The code was a mess. AI had generated features at unprecedented speed. Two months in, I had a product. I also had a codebase that scared me. Inconsistent patterns. Functions doing too much. Tests that passed but didn’t actually test anything. Comments that lied about what the code did. I’d traded velocity for debt. Now the debt was coming due. This is the dark side of vibe coding. Speed is addictive. Debt accumulates silently. Then one day you try to add a simple feature and it takes three days because everything is tangled. Managing debt isn’t about not having debt. It’s about having the right amount of debt and paying it down strategically. Why AI Code Accumulates Debt Faster AI code has specific debt patterns: Inconsistency: Each generation might use slightly different patterns. Small inconsistencies compound into chaos. Over-engineering: AI often generates more than
Day 29: Measuring What Matters: Is AI Actually Helping?
Jan 29, 2026 · original
I felt faster. Prompts flying. Code generating. Features shipping. The vibe was strong. Then I looked at my actual output. Features shipped per week. Bugs in production. Time from issue to deployment. The numbers told a different story than my feelings. I wasn’t faster. I was busier. More code was being written. But the important metrics were about the same. That’s when I learned: feeling productive and being productive are different things. If you want to know whether AI is actually helping, you need to measure. What Not to Measure Some metrics are useless or misleading: Lines of code: More code isn’t better. AI generates verbose code. You might ship more lines and less value. Prompts per day: Using AI more doesn’t mean accomplishing more. You could be prompting in circles. Features started: Starting is easy. Finishing is what matters. Time in AI tools: Time spent doesn’t equal value pr
Day 28: The AI Tool Landscape: When to Use What
Jan 28, 2026 · original
I use four different AI tools. Not because I can’t pick one. Because different tools are better at different things. Claude Code for codebase-wide changes. GitHub Copilot for inline completions. ChatGPT for exploring ideas. Cursor when I want AI deeply integrated in my editor. The tool landscape is confusing. Marketing makes everything sound the same. In practice, they’re different in ways that matter. Here’s my honest assessment of when to use what. Claude Code Best for: Codebase-wide operations, multi-file changes, complex reasoning Claude Code operates across your entire repository. It can read multiple files, understand relationships, and make coordinated changes. When you need to refactor a pattern that appears in 20 files, Claude Code handles it. Use it when: Changes span multiple files You need to understand how components relate Complex reasoning about architecture Large refactor
Day 27: Building Your Prompt Library: Capture What Works
Jan 27, 2026 · original
I wrote the same prompt three times last week. Each time I needed to generate tests, I wrote a new prompt from scratch. Each time it was slightly different. Each time I forgot something the previous version had. This is inefficient. When you find a prompt that works, save it. Categorize it. Reuse it. Stop reinventing prompts every time you need to do the same kind of task. Your prompt library is an investment. Build it once, benefit forever. What Goes in a Prompt Library Prompts that: You use more than once Took time to get right Work consistently well Apply to common tasks Don’t save: One-off prompts for unique situations Prompts that didn’t work Prompts that are just your project context Get the Starter Kit I’ve created a prompt library starter kit you can use right now: Download Prompt Library Starter Kit (ZIP) Or browse the templates directly: examples/prompt-library Library Structur

Found by rss-feed-index, which checks each feed once a month at most.

Same record as JSON: https://api.agentalog.com/api/feeds/fd_31daysofvibecoding_com_76866a79a8d4259d. More from this site: 31daysofvibecoding.com in the Feeds tab.