Click any tag below to further narrow down your results
+ game mechanics
(3)
+ careers
(2)
+ game design
(2)
+ speculative design
(1)
+ collaborative coding
(1)
+ ai
(1)
+ engineering practice
(1)
+ llm prototypes
(1)
+ elliot morris
(1)
+ theme vs mechanics
(1)
+ splatoon
(1)
+ game development
(1)
+ gray box prototyping
(1)
+ joe baxterweb
(1)
+ hiring
(1)
Links
Maggie Appleton, a research engineer at GitHub Next, shares how her Labs team explores possible futures for software by building prototypes, and offers practical techniques for doing speculative design yourself. She argues design engineers are well placed to turn theories about where software is heading into tangible artefacts.
- Her track record includes calling the rise of digital gardens (2020), the flood of AI-generated content on the open web (2022-23), and an explosion of home-cooked software and barefoot developers (2024).
- GitHub Next works by posting rough prototypes daily on an internal platform, grouping team-wide weak signals on a shared board, and then pushing promising bets toward production, with Copilot, Spark, Workspaces and Agentic Workflows as past examples.
- She frames design engineers as designers who make real decisions about state, data flow and architecture, and says agents now fill gaps when a prototype needs something the designer can't build alone.
Elliot Morris argues that prototypes used to force engineers to communicate clearly, surface real problems, prove competence, and engage with reality, but LLM-built prototypes break most of those benefits. He thinks the useful future prototype is a sharp, single-thesis experiment rather than a big, sprawling demo.
- Prototypes once delivered four bundled benefits: clear communication, early problem discovery, a visible competence signal, and forced contact with reality. LLM prototypes keep only the first of these reliably.
- LLM output tends to drift toward a generic "average" answer, so the builder can end up communicating something they didn't intend without noticing.
- Experienced engineers make rougher, smaller prototypes because they test one narrow thesis. Morris suggests the key question is now "what specifically does this prove, and why should I care?"
The piece walks through the old debate over whether game designers should start with story and atmosphere or with the core gameplay loop, then argues most strong games blend both. It leans on examples like Silent Hill and Resident Evil for theme-first design and Tetris, Celeste, and Super Meat Boy for mechanics-first.
- Theme-first helps emotional connection and guides mechanics, as in horror games where limited resources and slow movement build tension.
- Mechanics-first catches problems early, since gameplay can be prototyped and tested before themes and story are layered on.
- The recommended middle path is to prototype mechanics while holding a loose theme idea, then let the two evolve together through playtesting.
A 2019 r/gamedev discussion where experienced developers argue that game mechanics should be prototyped before art, using placeholder graphics to test whether the core idea is fun. Commenters back this up with examples like Splatoon's gray-box prototype and Zelda: Breath of the Wild's 2D chemistry prototype.
- Build a basic prototype with gray boxes or placeholders to test whether the mechanics are fun before investing in art.
- Art done too early can clash with the mechanics, forcing wasted work and cut assets, as one commenter learned on an early project.
- Art should lead only when it is a key selling point; otherwise it should serve gameplay and narrative.
Joe Baxterweb argues that game designers often blur mechanics, rules, and systems together, and offers his own cleaner definitions. Mechanics are the player's verbs, rules are the underlying logic that builds them, and systems supply the objects those verbs act on.
- Rules are the if-then logic of a game, and mechanics are made of rules. Small changes to a rule can make a mechanic feel completely different, such as coin collection in a platformer versus a VR game.
- Core mechanics like jumping or dialogue clicking define a game's character, so their feel should be locked in early rather than treated as superficial.
- Prototyping advice from Sid Meier: when testing a variable, double or halve it, since big swings reveal the effect of a rule change more clearly than tiny tweaks.
Felix Rieseberg, a hiring manager at Anthropic, argues that AI has made the traditional coding interview obsolete and that engineers without seniority can now move fast by building working prototypes. He offers a playbook for newcomers to get noticed by tying their work to business impact.
- Anthropic stopped giving coding interviews because Claude now outperforms candidates on small coding challenges, and top builders succeed regardless of how they do on them.
- Newcomers have an advantage in spotting friction and questioning assumptions that old-timers stop noticing, but they usually lack the status to get ideas funded.
- AI has cut the cost of execution, so a junior engineer can build a focused prototype over a weekend and skip the usual PRD and buy-in process. Keep it to one good idea, aimed at a business goal.
Teams can ditch rigid handoffs by pairing AI coding agents with every role in parallel. Early drafts turn ideas into working code instantly, shifting design and product feedback after prototyping and moving reviews before pull requests to boost quality and speed.
- Three shifts (non-engineers can prompt working prototypes, coding got cheap enough that upfront specs slow things down more than building, and parallel AI agents make human review the bottleneck) are killing waterfall handoffs.
- The fix: build rough drafts first, let every role (PM, designer, QA) work directly with agents instead of routing through engineers, and move validation before the PR instead of after.
- Adoption should ramp through three stages—throwaway prototype repos, prototyping in the real codebase with live design systems, then AI agents wired directly into production repos.
- Humans still own final pull-request review even as AI handles the first draft and early iterations.