This blog is open. Same person as the TikTok (@dormroomdev), same rule I’ve had since day one:
If I haven’t run it, I don’t post it.
Here’s why. Open-source Twitter and TikTok are full of accounts posting “10 GitHub repos that will blow your mind” — and half the time, the person posting never cloned a single one. The README looks great, the demo GIF looks great, and then you install it and it doesn’t even start. I’ve wasted enough evenings on repos like that.
So my process is boring on purpose:
- Clone the repo.
- Run whatever the README says to run.
- Actually use the thing — click the buttons, run the commands, break it if I can.
- Only then make the video.
It costs me an extra hour per video. It’s also the whole point. When I say a tool is fast, it’s because I watched it be fast. When I say “skip this one,” it’s because it crashed on me, not because the vibes were off.
What this blog is for #
TikTok is 50 seconds. That’s enough for a demo and a verdict, but not enough for the interesting stuff — the setup gotchas, the “here’s what actually died when I ran it,” the longer comparisons. That’s what goes here.
Expect three kinds of posts:
- Repo write-ups — the long version of my tutorial videos, with the commands and the caveats.
- My own projects — stuff I build, like DevTrack and idea-review. Building in public, including the parts that don’t work yet.
- Weekly AI Flex — every Friday I let AI build something it shouldn’t be able to. The blog post gets the behind-the-scenes version.
One post a day is the goal, matching the videos. If a repo isn’t worth your time, I’ll say so here too — just with more receipts.
First project post is already up: DevTrack, the CLI I built because I kept blanking at standup.