About CodeNook
$ one developer, a keyboard, and a habit of writing down what actually worked.
CodeNook is a game-development blog run by one working programmer out of Szczecin, Poland — a place to write down the parts of shipping games that live below the marketing. I've spent years on the code side of small and mid-size teams: gameplay systems, engine plumbing, the tools nobody sees. This is where I keep the notes, mostly so I stop relearning the same lessons the hard way.
It exists because most of what gets written about making games stops exactly where the interesting part begins — at the code. There are endless overviews of what to build and very little on how, at the level of a real engine, a real gameplay system, a real deadline. If I share a fix here, I shipped it. If I share a mistake, I made it.
What you'll find here
Long-form write-ups: postmortems with the actual frame times, architecture breakdowns with the code that shipped, tooling notes, and the mistakes I only understood in hindsight. Every post starts from a real problem in a real build, not a clean tutorial project. If I share a fix, I shipped it. If I share a mistake, I made it.
Who it's for
Programmers and indie developers who want code-level detail they can use — juniors reading to level up, mid-level devs comparing notes, and anyone tired of surface-level content. You should be comfortable reading code; I'll handle explaining the domain around it.
About CodeNook Pro
The articles are free to read. A monthly membership, CodeNook Pro, unlocks the downloadable source samples and project files, a private members' Q&A thread on every post, early access to new pieces, and a vote on what gets covered next. It's month to month, and you can cancel any time from your account. Membership funds the time it takes to profile twice and write things properly.
What this isn't
It's a blog, not a course provider or a jobs board, and nothing here involves wagering, prizes of money, or games of chance — the word "games" means video games, the software kind. Everything published is for learning.
Got a topic you'd like torn apart, or a correction? Get in touch — the best posts usually start as someone's question.
← Back to home