Building Strong Code Through Patterns
summary
Shows concrete patterns and runnable fixes: uses a simple finite state machine (enum + switch) to stop infinite Mario jumps and keep new input states from cascading bugs; implements a flyweight pattern plus a factory to load one mesh/texture set and spawn many goblins so four runtime objects map to two heavy instances, saving memory on low‑RAM devices; warns about singleton pitfalls (race conditions, test breaks, global coupling) and recommends IoC, assertions or passing dependencies instead.
AI-written summary · about
chapters (5)
related talks
30mMastering UIs with Finite State Machines
25mMastering UIs with Finite State Machines
28mState machines for frontend state management
24mLeveraging the Power of State Machines in Swift
46mTechniques for making reusable code
45mMastering UIs with Finite State Machines
58mImmutable Patterns of System Design; From Monolith to Agentic AI
26mInfinite Possibilities