The real founder coding vibe:

• You ship a small fix break 3 things

• You deploy confidently production crashes

• Local works perfectly Vercel says nah

• You spend 1 hour coding 4 hours debugging

• Slack notifications hit instant anxiety

Founders know the pain:
You re coding, marketing, fixing bugs, writing docs, and answering customer emails all at the same time.

What s your funniest or most painful founder-coding moment recently?
Let s vibe in the chaos

someone on my last thread pointed out the project file says what the project is, but not what changed since yesterday. i don t have a good answer for that yet.
what do you do, just let it read the git log?

We price in prepaid credits so the worst case is meant to be boring. You hit zero, generation stops, nobody gets a bill they didn't agree to.

Then we shipped a spend function that was writing bad balance events. The ledger drifted from what people had actually spent, so the ceiling I thought I had wasn't the ceiling. Nothing failed, nothing alerted, and the number in the config was still correct the whole time.

More of us are shipping client projects with AI coding tools now, and the build part has gotten fast. The handover hasn't. The client gets a working app but no idea where it lives, how to update a line of copy, or who to call when a domain renews.

Curious how others handle this:

• Do you host it yourself and charge a care plan, or move everything to the client's own accounts?

• What do you actually give them: a Loom walkthrough, a doc, an admin panel, nothing?

• How do you keep them from coming back six months later with "the AI broke it"?

Would love to hear what's worked and what's bitten you.

A new study tested 50 developers using Claude Code where the AI's architectural advice was secretly decided by a random coin flip.

The wild part: builders agreed with the coin-flipped recommendation 86% of the time, and changed their own minds 60% of the time when the AI pushed back. Because the model sounds so certain and polite, we assume it sees something we missed.

That test rewriting bug is so sneaky. I had a similar issue where an agent was asked to clean up a messy function, and instead of fixing the logic it just deleted three unit tests that were failing because it got lazy. CI turned green instantly and everything looked great on the surface.

Now I have a strict rule in our pipeline where code changes cannot modify anything inside the test folders without a separate human review.

Have you added any automated blocks to stop AI tools from touching test files?

Hi everyone, I just started an apprenticeship where I'm using Microsoft's Power Automate, Copilot studio and Service Now. However, this mean's there's very minimal coding involved(we weren't even told to install VScode), so I was looking for some good project ideas in AI/ML to do alongside, to keep my python coding skills intact?