Craft
Articles on the craft of a game programmer: what people in gamedev actually do, whether a studio needs its own engine, and what's worth reading to step on fewer rakes.
- Craft
More instances are needed, my lord
A sequel to the chronicle “Production has fallen, my lord”: the kingdom of Yundexburg builds a new castle in Mamsterdam, nobody checks the gates, the cartographers are cut by a quarter, and road signs are placed according to the length of horses’ tails. One day a mistake in the stables sends messengers down every road in the world, the registries choke, and Master Godfrid is summoned to court once more — to a contraption in the cellar labelled “Dismantle after the release” from Balthazar von Kludge.
- Craft
Where Complexity Comes From
The second part of “Dirty Games”: nobody writes complex code for fun — complexity arrives together with a number: 16 ms per frame, 5 GB of available memory, a patch-size limit, ten seconds to the first interactive frame. Broadphase levels from O(n²) to a SIMD BVH as the mechanism of buying complexity, why two constraints are worse than one constraint twice, how data-oriented design drags the cache line up through the whole architecture, hard and soft limits with a console memory budget, the Jevons paradox in gamedev, and constraints that are not in any document.
- Craft
Dirty Games
Why games with “dirty” architecture sell millions while games on beautiful engines with ECS and a job system sit in your backlog: a frame budget where logic for 200 enemies costs 0.05 ms, the cargo cult of GDC interfaces, Vampire Survivors on Phaser, Balatro on Löve and VVVVVV, a boring stack as risk management, a monolithic GameManager and a linear Tick versus an EventBus — and where simplicity does break: boundaries between data and logic, save games and certification.
- Craft
Play the good ones, don't play the bad ones
Fifteen years in gamedev and still no way to explain to your own child why their game is a bad one. Retention lives in every game you ever liked — from Elden Ring to Tetris — and the only thing that moved is where the cash register stands. Friction decides more than quality, three people in a lobby pin both BG3 and Miyazaki to the mat, and the arithmetic of an hour of content explains why «good» studios build services anyway.
- Craft
Lemons, games and the economics of remakes
Akerlof’s «market for lemons» applied to game engines: what gets sold is not the architecture but a demo scene built on bought assets, the engineering opinion is worth less than a morning coffee, and «buy, don’t build» assembles a game out of third-party modules that know nothing about your memory or your game. Where technical core competency goes, and why losing it ends in a remake conveyor belt.
- Craft
What consoles gave developers
Fifty years of console gifts to the developer: the Fairchild cartridge separated the game from the hardware, racing the beam on the Atari 2600 created a profession of its own, Exec on the Intellivision became the first SDK, and 10NES became the licensing model. Then Mode 7, the memory card, Xbox 360 achievements and the subscription that replaced the game — plus the bill that had to be paid for every gift.
- Craft
Production has fallen, my lord
A chronicle of the fall of Krivengard castle: a charter unifying every signal is rolled out nine days before a siege, Master Godfrid’s forgotten contraption dozes in the cellar, and a thrifty scribe left the eighth tower out of the registry. A fortress that had withstood eleven sieges fell without a single stone breached — and the post-mortem found nobody to blame.
- Craft
English instead of code
COBOL, SQL, 4GL, CASE, UML and No-Code all promised to rid the industry of programmers, and every time they spawned a new specialty with its own salary band. Why "natural language instead of code" runs into a ceiling: irreducible ambiguity, Rice's theorem, the discourse representation theory of Kamp and Heim — and the Jevons paradox, thanks to which cheaper code only grows the demand for developers.
- Craft
Victims of clean code
Why trading "10% of performance for programmer comfort" in gamedev hits both the games and the developers themselves: Martin's clean code as an extra layer of abstraction, cache misses and virtual calls versus SoA, the cost of every iteration and not just the runtime, and slowdowns that spread across the cyclic dependency graph of a studio, engines, and SDKs.
- Craft
Where a senior can grow in gamedev
Three fundamentally different growth paths after senior in gamedev: architect (system of systems), tech lead (technology and depth), and producer (product and market) — the price of each path, hybrids, super-producers, and the "toastmaster" archetype.
- Craft
On the "random" people in IT
A reply to the claim that "without a relevant degree, don't even bother trying to get into IT": the history of the game industry as a history of lawyers, homemakers, pilots, ushers, and canned-bean exporters — from Gary Gygax and D&D to Miyamoto, Iwatani, Roberta Williams, Will Wright, Kojima, Molyneux, Miyazaki, Notch, Eric Barone, and Davey Wreden.
- Craft
Why Soviet programmers didn't make GTA
Why the country that designed the Buran, the Tu-160, and nuclear icebreakers never made a Western-level mass-market game: a game as a large engineering task, where talented developers come from, back-of-the-envelope arithmetic for the socialist bloc, Silicon Valley's global "talent vacuum cleaner", a tour of post-Soviet gamedev from Tetris to S.T.A.L.K.E.R., Atomic Heart, and War Thunder — and why a "Russian Unreal" can't be conjured up on command.
- Craft
Three in a boat, poverty and dogs
An honest look at the state of the game industry in 2026: indies running on enthusiasm and options, service-game casinos, remasters of remasters, developers migrating into "subsidiaries" for a paycheck, and gamedev as the art of negotiating with yourself — where we're all in one leaky boat.
- Craft
About 10x programmers
Do 10x programmers exist, or is it a startup myth and a manager's dream: five real types of "fast" developers — the person fused with the project, the one who writes less code, DoItProperlyMan, narrow expertise, and the focus myth — and why 10x is always about accumulated context, not an innate coefficient.
- Craft
How not to confuse a dream, a portfolio, and a second job
On pet projects in gamedev: why a "couple-of-evenings" project turns into years of your life, how learning differs from writing your own engine, why a small library survives more often than an ambitious all-in-one, the cost of C++ for hobby projects, and how open-source quietly becomes a second job.
- Craft
On the joy of programming and the weightlessness of achievement
Reflections from a developer who caught the era when code was written by hand without AI assistants: why an achievement earned too easily feels weightless, how AI removes the "useful friction" and the flow state, and where a programmer's new mastery may lie — in architecture and depth of decisions rather than typing speed.
- Craft
Writing code is easier than writing a book about writing code
How the Game++ series on Habr grew into a book about pragmatic C++ and engine development: what "good" C++ is, the people who helped make the book happen, editing as a craft of its own, and a big block of answers to the frequent questions about writing and publishing it.
- Craft
Why university doesn't train programmers
Why classic university education doesn't turn students into programmers: teachers with no real-world experience, a vicious salary circle, programming as a hands-on skill like playing the guitar, studio mentorship and why programmers are made through self-teaching.
- Craft
Don't panic, you've just landed in AA+ gamedev
How not to panic when you land in a big AA+ studio with a multi-million-line codebase: navigating someone else's legacy, build systems, why seniors don't remember the code by heart, searching by user-visible strings, git history, code style and why the source is the ultimate truth.
- Craft
Just write code
A manifesto in the spirit of "just write code": while everyone else argues at the meeting about which board to move the ticket to, no Jira will ever write the bugfix. On working crap code, devalued titles, leetcode interviews, and the idea that if there are no bugs — you just didn't write any code.
- Craft
A couple of things a game programmer should know
A collection of sarcastic "laws" of game development: about std::move, undefined behavior, GameObject and ECS, cert submission and TRC, Heisenbugs, tech debt, // TODO and //TMP, managers, artists and Friday patches — the bitter truth of gamedev in one-liners.
- Craft
Game++. Building arcs
Game engine architectures and Conway's Law: the unitary (Big Ball of Mud) approach in Unity, layered in Unreal Engine, microkernel in CryEngine and O3DE, data-driven in Dagor, monolithic in X-Ray and micro-modular in Godot.
- Craft
Game++. Juggling STL algorithms
Why STL algorithms are "conversational" C++: they show What you do, not How; they remove bounds, empty-collection and "smeared perf" bugs and give you compiler-grade code. The history of EASTL, iterators and a big algorithm cheat sheet.
- Craft
In Spain, all programmers are seniors
How working in Western gamedev studios differs from post-Soviet teams: "snitching," not touching others' tasks, communication through the PM, excessive politeness, respect earned through solved tasks, context-based vs. detailed communication, and anchor phrases.
- Craft
Good books for a gamedev AI programmer
A reading list for a game-AI programmer with personal takes: AI for Game Developers, Game AI Pro, Game Engine Gems, The Pyramid of Game Design, Behavioral Mathematics for Game AI, and AI Game Programming Wisdom.
- Craft
What is C++ in gamedev?
Why gamedev is locked into C++ and how the language lives inside an engine on three levels: hardcore number-crunching, "ordinary" C++ with scripts and hot-reload, and a meta level with reflection and code generation.
- Craft
What else should a game programmer read?
A follow-up list: Joel on Software, Blood, Sweat, and Pixels, the Doom 3 source code, MISRA C++, EASTL, daScript, GDC talks and blogs worth reading.
- Craft
What should a game programmer read?
A reading list of books, blogs and repos for a game programmer: from Code Complete and Effective C++ to Game Engine Architecture, Game AI Pro, GDC and awesome-lists on GitHub.
- Craft
Why you [don't] need your own game engine
Why studios and indies build their own engine instead of Unreal/Unity: is it expensive, is it hard, hands-on experience with Frostbite, Unity and Dagor — and why bespoke tech moves the industry forward.
- Craft
Are you sure you want to become a programmer in gamedev?
An honest look from the inside: what programmers actually do in gamedev, interviews, overtime, engines and their schools, studio traditions, designers — and why it's still worth it.