how “shimmer… where?” became an entire universe
The accidental sentence behind Shimmerwhere, and why a project name can become a place to live.
develop this story →
A TECH DIARY • FROM BEFORE THE CODE
A screenshot is proof. A polaroid is a memory. I kept the crooked ones, the creases stay.
The accidental sentence behind Shimmerwhere, and why a project name can become a place to live.
develop this story →
obsessing over rain on interfaces · learning x86 assembly · building quiet systems.
the plan →Not a highlight reel. The half-formed thoughts, strange names, rebuilds, mistakes, and useful little realizations get to stay.
The accidental sentence behind Shimmerwhere and why a project name can become a place to live.
open entry ↗Broken toy cars, old gadgets, PSPs, and the long route from curiosity to computer science.
open entry ↗PurrSona, five feline archetypes, one gradient-boosting model, and an ONNX escape plan.
open entry ↗Small constraints for a brain that wants every project to become a cinematic universe before lunch.
The rule is simple: code, document, or understand one thing each day. The artifact can be tiny. The curiosity cannot be fake.
Give the idea somewhere physical to exist before asking it to be beautiful.
Write down the wrong turn. Someone else—or future you—will need it.
“Alive and shareable” is a better milestone than “perfect and imaginary.”
Coding between glasses of iced tea, slow sunsets, and colorful sketches — the season where you remember rest is also part of the build.
I build tiny universes in code. If you are learning in circles, overthinking one semicolon, or waiting to feel ready: you are not late. You are developing.