How to Lose Your Feature Bloat?
summary
Explains how software projects accumulate excessive feature bloat and offers practical ways to shed it. Covers identifying unnecessary features, decision criteria to remove or simplify them, and approaches (process and tooling) to keep a PHP codebase lean and maintainable.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:28Developer's story
- 6:23Accidental vs essential complexity
- 7:27Feature overload definition
- 10:59Why not drop the app
- 12:04Overloaded brain analogy
- 13:05Pillar 1: Define the why
- 16:32Cover story workshop
- 17:58Octopus character creation
- 19:44Pillar 2: Card sorting
- 22:09Pillar 3: User tests
- 23:13Five-second test
- 26:01Moderated user tests
- 27:47Pillar 4: Avoid bloat
- 30:59Summary and design thinking
- 33:26Q&A
related talks
37mHow to Lose Your Feature Overload
45mWhy and How to Split an iOS App into Microfeatures
51mFeature Flip to Achieve Flow
58mIntentional Code - Minimalism in a World of Dogmatic Design
17mHow to deal with technical debt in fast-paced environment
48mUnderstanding Feature-Sliced Design
01mThe Path Through Legacy: Delicate Balance Between Tolerance and Phobia
20mStarting Module Separation from New Feature Development