posts
A practical product case study on Tunic, covering knowledge progression, manual-page discovery, readable secrets, publisher fit, difficulty risk, and how Andrew Shouldice made nostalgia operational rather than decorative.
A practical product case study on Return of the Obra Dinn, covering deduction design, information architecture, visual constraints, production risk, player trust, and why Lucas Pope made mystery feel like labor rather than exposition.
A practical product case study on Slay the Spire, covering deck-building clarity, early access balance, streamer feedback, run structure, card economy, and the product lessons behind a genre-defining indie success.
A practical product case study on Outer Wilds, covering knowledge-based progression, time-loop structure, publisher fit, mystery protection, spoiler-sensitive marketing, expansion boundaries, and why Mobius Digital made curiosity the real upgrade system.
A practical product case study on Spelunky, covering freeware validation, procedural level design, player blame, commercial remake strategy, daily challenge culture, sequel discipline, and why Derek Yu built a platformer that became a genre reference.
A practical product case study on Cuphead, covering hand-drawn animation, boss-rush positioning, difficulty, platform timing, brand expansion, DLC, Netflix adaptation, and why Studio MDHR made production difficulty part of the product.
A practical product case study on Shovel Knight, covering Kickstarter, retro positioning, platform strategy, stretch-goal debt, free campaigns, character branding, amiibo, and why Yacht Club Games turned an 8-bit homage into a durable product line.
A practical product case study on FTL: Faster Than Light, covering Kickstarter timing, pausable real-time pressure, event writing, ship systems, replayability, iPad fit, and why Subset Games made a small strategy game feel endlessly dramatic.
A deep engineering essay on the philosophy behind Plumego. This article explores why explicit systems outperform implicit ones in long-lived software, how hidden abstractions accumulate technical debt, and why Plumego is intentionally designed as a framework that forces clarity, ownership, and architectural responsibility.
A deep, end-to-end walkthrough of building a real-world backend service with Plumego. This article traces a request from HTTP entry, through routing, middleware, context, use cases, domain logic, and infrastructure, explaining architectural decisions and trade-offs along the way.
A comprehensive, in-depth decision guide for evaluating Plumego as a Go framework. This article examines architectural trade-offs, team maturity, system lifecycle, operational concerns, and long-term maintainability to help serious Go teams decide when Plumego is the right choice.
An advanced, in-depth guide to Plumego. This tutorial explores real-world architecture patterns, middleware composition, context design, lifecycle management, observability, and building production-grade Go services with Plumego.
Plumego is a deliberate, explicit Go framework designed for long-lived services, disciplined teams, and engineers who value clarity over magic. This article provides a comprehensive introduction to Plumego’s philosophy, architecture, and practical usage.
Birdor Tools is a quiet, reliable hub of practical tools, clear engineering notes, and thoughtful experiments around modern software. Here is our vision, what’s live today, and what’s coming next.
A development update introducing unified UI badges, a new prebuild changelog pipeline, and the major launch of the official 'What is Birdor' product overview page.
A development update covering HS512 support in the JWT Debugger, improved JSON tree collapsing, and the launch of the Birdor Changelog system.
A calm, friendly, and practical 20-chapter Python beginner handbook designed for modern developers.
A practical, Birdor-style comparison of Python, Go, and Rust — strengths, weaknesses, performance, concurrency, ecosystems, and when to choose each.
A development update covering new SEO metadata for all tools and the addition of a GitHub icon to the site header.
Lua for Game Development is a calm, practical book for developers who want to use Lua as a real production tool: game loops, ECS, AI, UI, multiplayer, tooling, and deployment — with clean examples and engine-agnostic patterns.