notes.visaint.space
Vi Saint Notes
The thinking behind visaint.space
A system is what it does, not what it was supposed to do. Design's the same — it was never just how something looks, it's how it works. It's in everything we touch: what we're able to do, what we're quietly prevented from doing, and how much friction sits between wanting something and getting it.
I'm endlessly curious about those decisions, especially in software, where design gets to be invisible and consequential at once. This is where I look closely at all of it.
What's here
Ideas, links & deep dives
Sometimes an idea only needs a paragraph before it's done being an idea, so it gets a short post and we both move on with our lives. Sometimes someone else built or wrote something genuinely clever and I have to point at it like a kid who found a good rock. And sometimes a topic refuses to fit in a paragraph no matter how hard I squeeze, so it gets the long version, footnotes and all, whether it asked for them or not.
No fixed format, no calendar — closer to a mixtape than a notebook. Mostly I'm writing about whatever's currently happening over at visaint.space, plus whatever unrelated thought has moved into my head and refuses to pay rent.
Good places to start
The posts people actually come back to.
AI Coding is Gambling
Coding with AI feels less like a craft and more like pulling a slot machine lever.
.txtKeep It Simple
Web dev keeps overcomplicating the basics — sometimes the plainest tool really is the right one.
.txtThe iPod
Two stories in one: a life shaped by Steve Jobs, and the scramble behind the original iPod.
.txtAutomation Fears
We've feared automation stealing jobs for as long as it's existed — the reality is weirder than that.
.txtMove in Faith
On Kanye, belief, and learning to move through life with faith instead of certainty.
.txtNever-Ending Improvements
A running log of the small tweaks and redesigns keeping this blog just right.
Hi, I'm Vi
Creative Technologist, which is the professional way of saying I design things and then can't stop myself from also coding them, badly, at an hour I'm not proud of. I care more about a considered interface than a fast one — a fight I mostly lose against my own deadlines, but I keep showing up to it anyway.