Can vs Should
We are downstream of canivibecodeit and we like it that way. They answer whether an agent can replace a tool. We take everything they said yes or kinda to and ask what happens when it breaks. Most of the time we agree. These are the 40 where we don’t.
AI will write you a vault in an afternoon. Your entire digital life is the test suite.
An invoice is a legal document. Your off-by-one is now a tax discrepancy.
Small list, same law. The compliance floor does not scale down with your subscriber count.
Paid memberships mean people are owed access. Access has to survive your enthusiasm.
A transcript of a call someone didn’t know was recorded isn’t a side project. It’s evidence.
An automation hub is a box holding every API key you own, wired to the internet.
Sync is the hardest problem you will ever underestimate, and the loser is your notes.
Twenty lines of code. But every link you shorten is a permanent promise to keep a server alive.
The one category where “I rolled my own” has never once been the happy ending.
Encryption is a library call. Not losing the only copy of your keys is a business.
Your rounding bug is not a bug. It is a discrepancy on a filing with your name on it.
An autonomous agent with delete permission on your inbox is a very fast way to lose something.
You are building a box that runs strangers’ code. That box is a cryptominer with extra steps.
Lifecycle email means automated messages you did not personally read going to real customers.
Courses, community, email and payments. Pick one to vibe code. Not four with a checkout attached.
Nobody has ever regretted paying someone else to own their sender reputation.
Transactional and marketing mail have different rules, and mixing them poisons both.
Your reputation as a sender is an asset you can destroy in one bad loop and never rebuild.
Sending bulk email is 5% code and 95% not getting your domain blacklisted forever.
The unsubscribe link is the regulated part, and it is the part you will implement last.
Selling a course means owing access to it for years. Your side project does not have years in it.
A file rule with a bad glob doesn’t warn you. It quietly moves your tax returns somewhere.
Postgres you can run. Auth is the part where confident code is quietly wrong.
Phone calls are the most regulated recording surface there is, and you want a cron job on them.
Recording the call is the easy half. Being allowed to is the half nobody prototypes.
Port-forwarding your house is a decision, not a feature.
An internal tool is just a production database with a friendlier delete button.
An AI that answers your customers wrongly is a support ticket that scales.
A dropped support email is invisible. You find out from the refund request.
Unofficial messaging APIs get numbers banned, and the number is usually a real business’s.
Retries are the feature. A loop without them silently drops work; a loop with them sends it twice.
Video hosting is a bandwidth bill wearing a product costume.
An open redirect you built yourself is a phishing kit with your brand on the envelope.
Static hosting is easy right up to the first traffic spike, the first cert, the first outage.
Every platform’s API breaks on a different Tuesday. That maintenance is the whole subscription.
Twenty-eight channels means twenty-eight ways for your Saturday to become an integration day.
It holds the keys to your public voice. A retry loop at 3am posts the same thing eleven times.
You will replace a $20 bill with a pager that goes off on Christmas.
Reselling access to a platform that does not want you reselling access is a business model with a countdown.
Your error logs are the least-secured copy of your most-sensitive data.
To be completely clear
When canivibecodeit says YES it is answering a feasibility question, and an agent really will produce a working password vault in one session. This site answers the next one. “It works” and “you should run it” are different claims, so a row where the two verdicts differ is two questions with two answers. Their data seeded this site and their build prompts are linked from every page — go and read them.