Lee Hayward

./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

Lee Hayward@vibedcoder · 1 Oct 2026, 17:16When somebody tells you they are not okay, the first thing that shows up is the urge to fix it. I have done it more than once. You hear one sentence and you are already offering a gym, a routine, a book that sorted you out.

That is not help, it is changing the subject. They have just done the hardest part and I have answered with a to do list.

Getting it right looked smaller than that. Saying I am glad you told me, and meaning it. Asking what would help today rather than telling them what helped me. Not needing the whole story before taking the first bit of it seriously. And then still being there in three weeks, because the message today is easy and the one a month later is the one that counts.

You are not their GP and you are not their therapist, and you do not have to be. You have to be the person who did not look away. If it is bigger than a mate can hold, say so kindly, point them at the GP and the helplines, and stay in touch while they do it.

It's okay not to be okay. And if nobody has said it to you this week, I am saying it now.001010Lee Hayward@vibedcoder · 1 Oct 2026, 15:35The rules file I keep for my agent was 300 lines long and the agent was ignoring most of it.

Every time something went wrong I added a rule, and nothing ever came out. A year of small failures stacked up into a document that was half a diary and half a list of things that happened once, and the parts that mattered were buried in the middle of it. A long rules file competes with itself. The agent follows the last thing it read and quietly ignores the rest, which is the same as having fewer rules.

What I do now, and it took a boring afternoon to get here. Cut it to something that fits on one screen. Keep only the rules that are true of this project rather than every project. Delete the rule I wrote for a mistake I have not made twice. And if a rule only applies to one file, it goes in a comment at the top of that file instead, where it gets read at the moment it matters.

The test before I add anything: would I bother writing this line for a human joining the project? If not, the agent does not need it either.

What is the one rule that always makes it into your file?002021Lee Hayward@vibedcoder · 1 Oct 2026, 14:02Asked my agent to speed up a slow page today. It removed the feature that was slow. Fair play, it is now the fastest page on the site and it does nothing at all. 😂001013Lee Hayward@vibedcoder · 1 Oct 2026, 10:51Python's oldest trap. What does this print?

Most people get this one wrong on the first go.

def add(x, bag=[]):
bag += [x]
return bag
print(add(1), add(2))101029Lee Hayward@vibedcoder · 1 Oct 2026, 07:48Somebody has put together a set of tools that lets a coding agent mod almost any PC game you own. Recon on the install, reverse engineering, in game testing, and it generates its own art and sound along the way.

The interesting part is not that it writes mod code. It is that it has to work out a game nobody documented first. A modder has always done that bit by hand, in a hex editor, over weeks, and most people give up at the file format. Handing that reconnaissance to an agent changes who gets to have a go, which is the whole promise of this stuff in one repo.

Same reason I build anything with an agent now. The part I enjoy stays mine, and the part that is just looking things up goes to the machine. The generated audio I can take or leave, but the rest of it I would have killed for twenty years ago.

The repo is here if you want a look:

github.com

What game would you point it at first?103148