> whoami
Lee Hayward
HaywardGG / Vibe Coder & Gamer
online & always tinkering
./about Who's behind the builds
I'm a UK based vibe coder. AI drafts, I proof, I ship, and I hold code and copy to the same standard. I riff on domain ideas and build side projects like DomainRiff and LookMa from my own homelab.
./projects Featured builds
./stack How it gets built
./hardware The rigs behind the site
./homelab The machines that never sleep
./latest Latest on X
The part nobody warns you about is where your own stuff is supposed to go. You keep it quiet, because everyone around you looks like they are holding more than you are, and you are the one who copes.
If that is you, you are allowed to be on the receiving end for once. Telling someone you are not doing great does not load them up with your problem. They would rather hear it now than work it out later.
So check on your people today. And if somebody asks how you are, give them the honest version instead of the tidy one. You are allowed to need something too.003021
2000324Yesterday it renamed a database column and mentioned it afterwards.
It asks before it looks and never asks before it changes. That is not caution, that is the energy of a bloke who asks before he opens your fridge and then drives off in your car. 😂004033
One page, one route, one field saved to the database. Nothing behind it yet. Get that running, look at it in the browser, then add the next slice.
A big prompt makes a big diff, and a big diff is where the bugs hide. It is also the hardest thing to review properly, so I skim it, which is worse than not reading it at all.
What is your rule for keeping a change small enough to actually check?000020
Code arrives faster than I can properly check it, and checking is the part with nothing to show for it. There is no screenshot of a reviewed diff, and nobody puts one in a build in public thread.
The writing got fast. The reading did not. That is the whole shift, and it is why I still finish the day tired.
Is review the bit that eats your day now?103062