| codeberg | https://codeberg.org/superseed |
| codeberg | https://codeberg.org/superseed |
Instead of using git as a database, what if you used database as a git?
Translation for lay(ish) people
“Move fast” : management decisions are absolute P0 and based on some billionaire’s last tweet. Everything else goes in the backlog. Especially error reports.
“Act like an owner” : be ready to take the fall when the whole thing falls apart (but actually fixing stuff is for a mythical backlog sprint)
“Thrive in ambiguity” : everything is P0. You get to figure out which are important. Hint: probably not the fixes.
So, you want me to code in a language that has no formal specification, no test suite, that changes continuously, where builds are not reproducible, where results depend on a hidden state in a build cache that can't be backed up, where I have to pay for each compilation, where I have to continuously send a copy of my code to a third party, and that might disappear with no notice?
Geee, vibe coding looks FUN!
"As fun as it is to rib on Mozilla, the web needs Firefox. I feel for the Firefox developers who actually care. State of Mozilla will inspire no one. The sloppy prose are borderline unreadable. The presentation is designed to stop you reading."