Somewhere around the blocks
Joined April 2013
- Tweets679
- Following990
- Followers205
- Likes2.1K
Rule I follow with AI agents:
After 2–3 failed attempts on the same bug, stop.
Stash the changes. New session. Better evidence.
Persistence helps humans. It confuses agents.
8
Write every piece of software as if you can’t patch it later. Smart contracts taught me that. It’s a good habit everywhere.
5
Tests aren't for engineers only.
A test is just: "when I do X, Y should happen", written down so the computer checks it every time.
Ask your agent to write one for every bug it fixes. The bug never comes back quietly.
8
Your deploy failed.
Don't scroll to the bottom of the log. Scroll to the FIRST error.
Run the build locally. Give that exact error to your agent. Ask for the cause before the fix.
13
Pushed your API key to GitHub?
Deleting the commit does NOT un-leak it.
Rotate the key in the provider's dashboard. Now. Then move it to an environment variable.
23
Unpopular opinion: "I'll walk it every day" should come with a 12-week trial period.
Agree or disagree?
petprep.si/
8
You don't need to learn to code to build with AI.
You need to learn to:
– define what done means
– read a plan
– test like a user
– check what changed
– ship safely
That's the job now.
8
5/6 Fix: turn on RLS for every table and write policies like "users can only read rows where user_id = their id". Then test with a second account.
1
6
Before you start a feature, write one sentence:
"The user can ___ so that ___."
If you can't write it, the AI can't build it.
12
Kids promise to walk the dog. Parents end up doing it.
I'm building PetPrep: a 12-week AI pet simulation with real steps, real feeding windows and a live dashboard for parents. Objective proof before a real pet comes home.
petprep.si
1
28