Why I Learn to Code in the Dark (And What Impostor Syndrome Taught Me)
September 2026
If you've spent any time on this site, you've probably noticed there's no headshot anywhere — no "about the founder" photo, no name in the credits. That's not an accident, and it's not a branding gimmick either. It comes down to one honest reason: the work should be judged on its own, not on who's doing it or what they look like while they do it.
That idea turned into Coffee & Code, a side series on the channel where the goal isn't to teach a specific skill — it's to talk plainly about what learning to code (or teaching it) actually feels like, without performing confidence you don't have yet.
Impostor syndrome doesn't wait until you're "ready"
Almost everyone who picks up coding hits the same wall: a nagging sense that everyone else already gets it, and you're the only one faking your way through. It shows up whether you're three days into your first "Hello World" or three years into a job title that says you should already know this. The uncomfortable truth is that feeling doesn't really go away on a schedule — it fades in proportion to how much you've actually built, not how much time has passed.
That's part of why staying anonymous made sense. Without a face attached to the channel, there's no persona to protect, no expert reputation to defend by hiding what's still being figured out in real time. A tutorial can just be a tutorial, and a mistake can just be a mistake — not a crack in some carefully built image.
"Tutorial hell" is a symptom, not a personal failing
If you've watched enough beginner content, you've heard the phrase "tutorial hell" — the loop where you follow tutorial after tutorial, feel productive in the moment, and still can't build anything on your own once the video ends. It's easy to read that as a discipline problem. It's usually not. It's what happens when a tutorial optimizes for the viewer feeling good instead of the viewer being able to do the thing independently afterward.
The way out isn't more tutorials — it's smaller, uglier, self-directed projects. Rebuild something you just watched without the video open. Get it wrong. Google the error instead of rewinding. That's slower and much less comfortable than following along, and it's also the only thing that actually breaks the loop.
What this means for how Dev in the Dark teaches
Every project on this channel — the Rainbow Website series, the Python Projects playlist, the Math Behind the Game academy workshop — is built around the same idea: show the real, sometimes-messy process of building something, not a polished highlight reel. If a concept is confusing, that gets said out loud instead of glossed over. If something breaks on camera, it stays in the video.
That's also why the academy workshop leads with math baked into a real project instead of a worksheet: the confusion of "why does this matter" disappears the moment a variable visibly changes how a game character jumps.
If you're in the middle of it right now
If you're staring at an error you don't understand, or you just finished a tutorial and have no idea how you'd build the same thing from scratch — that's not a sign you're bad at this. It's the normal, uncomfortable middle part that everyone glosses over when they talk about "learning to code." The only way through it is the same for everyone: build something smaller than you'd like, without the safety net, and let it be bad the first time.
Want more of this? Subscribe on YouTube, or check out the custom course and academy workshop if you'd rather learn with direct feedback along the way.