I never planned to make a game — the constraints chose the scope
Building a strategy game alone meant cutting scope. The list of constraints ended up choosing every mechanic in the game by itself.
Tag
A software career: seniority, responsibility, changing jobs and the skills that last.
There are 24 posts with this tag.
Building a strategy game alone meant cutting scope. The list of constraints ended up choosing every mechanic in the game by itself.
There is no right company type — only wrong matches. Closing the series: what each type teaches, and eight questions to ask in your next interview.
How to get a solid grasp of a codebase you've never seen before: understand first, refactor later.
Growth is a staircase, and the same thing breaks on every step: the capacity of informal coordination. Reading the transition from three desks at once.
The first question asked when production goes down sets a company's culture for years. The human side: fear, silence, and what changes later.
The status meeting isn't an information tool, it's an insurance policy. A critique that takes meetings seriously before taking them apart.