AI • Engineering • Shipping • Cloud • Infra • Security Building ideas into products DM for collabs
Bucuresti,Romania
Joined October 2009
- Tweets2.7K
- Following2.7K
- Followers1.8K
- Likes6.6K
Standup, translated:
"Almost done" = the hard part hasn't started
"Quick fix" = I don't know why it works
"Should be fine" = I didn't test it
"Blocked" = waiting on an answer I never asked for
Ask "what's left?" instead of "how's it going?"
Clean code isn't short functions or perfect names.
It's code the next person can change without asking you.
The test: could someone fix a bug in this file while you're on vacation?
Not a security plan:
"We use AWS, so it's secure."
"The AI said the code looks safe."
"We'll hire someone after the raise."
"We passed a pentest two years ago."
A plan is a list of who can access what, and what you do the day it leaks.
Dear vibe coders:
How many users does your app have?
And what's the worst thing that broke once real people started using it?
"It's a simple CRUD app."
It also needs: login, password reset, roles, audit logs, rate limits, backups, data export, account deletion and someone on call.
The CRUD is a weekend. The rest is the product.
By clicking "Approve" you agree that:
1. You read every line
2. You understood every line
3. You'll be the one paged when it breaks at 3am
Most approvals are a contract nobody read.
Famous last words in prod:
1. It's just a config change
2. Works on my machine
3. That key is only used in staging
4. Nobody would ever guess that URL
5. The backup job runs every night, I think
6. Quick hotfix, no need for review
7. The migration is backwards compatible
8. What could go wrong?
What's yours?
Friday deploy, a haiku:
"Small change, should be fine."
Laptop closed at 5:04.
Pager wakes at three.
No rollback plan? Then it isn't a small change.
How to never ship:
1. Start a second thing before the first is done
2. Rename the variables one more time
3. Wait for the perfect week
4. Ask for feedback, then wait for all of it
If you know what a prompt, churn, MRR, GTM and a 3am rollback are…
we should probably connect 🤝
Let's connect!
More code isn’t better software. Never was.
We will all be learning in coming weeks & months, that most human-made software:
▫️ Was really slow
▫️ Had many security vulnerabilities
▫️ Was under-specified and incorrect
AI will rewrite it all. Many times. It will make it fast, cost-efficient, and secure. It will think about failure modes we couldn't wrap our heads around.
It will prove, formally verify, load test, harden. It will turn memory-unsafe foundations into robust, optimized ones. If you ask, it'll thoroughly document it, teach you about it, make diagrams, animations, and slide decks.
In many ways, we are witnessing the true birth of software engineering.
You have 40 open dependency update PRs. Nobody merges them because one might break something.
So prod runs old libraries, known holes included.
Merge the security fixes every week. Batch the rest once a month.
Sales promised the feature on a call.
Engineering found out when it showed up in the contract.
One rule: no date goes to a customer until the person building it has said it out loud.
Your laptop died. Rebuilding your dev setup took two days.
Every tool, alias and config lived only in your head.
Put it in a script and a dotfiles repo.
Next time it's an hour.
What's your plan if your laptop dies right now?
A 50-line PR gets 12 comments.
A 2,000-line PR gets "LGTM" in 4 minutes.
Now AI writes the 2,000-line ones.
So who's actually reading your codebase?