Your tests pass. Your bug ships. Last week I shipped a bug tests couldn't catch. System reached "success" without posting the review. So I added postconditions 🧵

I just published Your Tests Pass. Your Bug Shipped Anyway. buff.ly/06ssr5B

Most people misunderstand what "building in public" means — and it's hurting their results. They think it's about sharing wins. In reality, it's about sharing the process (especially the messy parts) 🧵👇

Your pipeline works. Can you prove it? Last week I couldn't answer: "Can our AI run twice per request?" So I built a state machine to prove it's impossible 🧵

I've been creating a lot, but not all of it is aligned.Time to get focused.Right now, I want to be known for helping developers build in public and ship consistently 🧵👇

Your tests pass. Code review approves. Staging looks perfect. Production breaks anyway. Here's what tests miss 🧵

Want to be the best developer in 1 year? Here are 5 books that changed how I code, think, and build. Not theory. Real, applicable stuff 🧵👇

Two types of developers: Type A: Perfects tutorials for 6 months, never ships Type B: Ships broken projects, learns by iterating Which one are you? 👇

Are your fallbacks actually working or are you just hoping? I stopped assuming and started breaking things on purpose. Here's what I learned 🧵

Your system makes 1000 decisions per day. Can you explain any of them? "Why didn't my PR get reviewed?" should take 10 seconds to answer, not 10 minutes of log archaeology. Here's the fix.

12 months ago, I wouldn't have had the guts to post my code publicly every day. Now, I don't just do it — I teach others how to build in public. Here's what changed 🧵👇

I added a second server to my app. Everything broke instantly. Duplicate notifications. Exceeded rate limits. Servers fighting each other. This is distributed systems. Most learn it the hard way in production. Here's the fix.

Here are 7 tools I use every week as a full-stack developer — and why I love them 🧵👇

What breaks when you scale from 1 server to 2? Everything. After 9 days building MergeSense, I asked this uncomfortable question. The answer forced me to rethink how I design systems.

Here's my step-by-step process for going from 0 to deployed full-stack app in 30 days.If you're trying to ship your first real project (not a tutorial clone), here's what worked for me 🧵👇

Your AI tool will crash from its own success. I built MergeSense for 8 days. Then realized: I never tested what happens when 50 PRs arrive simultaneously. Ran the numbers. 50 concurrent requests = 1GB memory. My server: 512MB. Crash.

If you're struggling with staying consistent while coding full-time, try this instead.Capture, don't create. Here's what I mean 🧵👇

Every founder asks the same question about AI tools. "How much will this actually cost me?" Most companies can't answer with data. I just built the system that does—in 290 lines of code, no database required.

New month, new energy. Here's what I'm focusing on in February 🧵👇

Day 7: I didn't ship features. I shipped accountability. No AI improvements. No performance gains. Just the boring work that lets you answer "why?" when production breaks at 3 AM. This is what separates demos from systems you actually own. 🧵👇

I recently experienced a surreal moment at work. We had a project slipping down the backlog for weeks because the estimated effort was too high. We spent days in meetings debating the approach. Then a coworker just... did it. Used AI to scaffold the whole thing in one day.

Want to get better at building in public, shipping consistently, and growing as a developer? Follow these 5 devs doing it right 🧵👇

Want to get better at building in public, shipping consistently, and growing as a developer? Follow these 5 devs doing it right 🧵👇

Day 6: I integrated Claude AI into MergeSense. The easy part: 20 minutes The hard part: 6 hours The easy part was making an API call. The hard part was making it work when the API times out, returns garbage, or the network dies. Most build-in-public posts show the demo. 🧵👇

One line I keep coming back to is: "Done is better than perfect." Simple. Overused. But it changed everything for me 🧵👇

Day 5 of building MergeSense: I spent 6 hours refactoring code no one will ever see. No features added. Just replacing boolean flags with production-grade risk detection.

Fill in the blank: I wish more people knew _____ about building a career in tech. My answer: You don't need permission to start. What's yours? 👇

The best code reviewers know what to ignore. Today I documented what MergeSense will never comment on. This is a permanent exclusion list—things the system will detect and deliberately ignore.

Quick check-in on Day 11 of Creator Camp. No big wins today. Just progress. And that's enough 🧵👇

I spent today architecting an AI code reviewer. Wrote zero code. Made all the important decisions. Because in software, architecture is choosing what not to build.

Mornings used to feel chaotic until I built a workflow that actually works for me. Here's how I structure mine now 🧵👇

If I lost everything and had to rebuild my dev career from scratch today, I'd follow this exact plan. No shortcuts. No network. Just these 3 steps 🧵👇

We've been calling it the wrong thing for decades. It's not code review. It's decision review.

If you've been feeling like you're the only dev struggling with consistency, you're not imagining it. You're not alone 🧵👇

The best code reviewers ask fewer questions, not more. Here's what senior engineers actually look for in the first 60 seconds of a PR.

Here's how I break down my week to stay productive and sane as a full-stack developer. It's not perfect, but it's real 🧵👇

Most AI code reviewers are wrong about what code review actually is. They think it's about finding deviations from patterns. It's not.

My best code doesn't come from my desk. It comes from my 2 AM debugging sessions, coffee shop chaos, or walking around the block. Here's the environment that fuels my creativity 🧵👇

🧵 Day 14/14: The Complete Framework How to build your application — not just fill it out. 14 days ago, I applied to @Buffer by building in public. Today, I’m sharing the full framework so you can do the same.

I need your help. What's your best tip for staying consistent with content creation as a dev? Thread with your go-to strategy 🧵👇

Day 13/14: What this journey actually taught me. Yesterday I submitted my application to @Buffer. Today I realized I’m not anxious about the outcome. Not because I’m confident I’ll get the job. But because this stopped being about a role.

Here's how my content system actually works in practice. Real scenario from yesterday 👇🧵

Day 12/14: I’ve submitted my application to @buffer. Not a resume click. A 12-day build-in-public journey. 6,500 lines of code. 10,000+ words. One goal: build first, apply second.

My dev days used to feel chaotic — until I built my content system. The before/after that made posting as automatic as my CI/CD pipeline 🧵👇

Day 11/14: The quiet day before submission. No new code. No content. No breakthroughs. Just a checklist and 11 days of work—reviewing everything one last time. This is where good applications become great ones.

If you've been thinking about building in public, sharing your dev journey, or creating tech content — this is the perfect time. Here's why 🧵👇

Day 10/14: I recorded a video explaining my work—and it terrified me more than debugging production at 2 AM. No teammates. No feedback. No room to adjust. Just async communication. This is the hardest part of remote work.

Building consistency is hard, but it's easier with friends! 💙 As a Full Stack Dev (900+ LeetCode | MERN • Next.js • AI), I've learned: Consistency beats perfection. That's why I'm joining Creator Camp by @buffer 🏕️ Free 30-day challenge • Jan 19-Feb 13 Thread 🧵👇

Day 9/14: Building for @buffer, I Stopped Coding Today After 8 days of building, I did something counterintuitive: I stopped adding features and started reviewing. This is the hardest part of engineering—knowing when "good enough" is actually good.

Day 8/14 Spent 6 hours writing my Buffer application. Shipped 0 lines of code. Harder than building features. Lesson: senior work = explaining why, not just what. Specificity, systems thinking, and admitting when you were wrong matter. Writing is engineering.