Review: "Getting Real" by Jason Fried

This is Jason Fried telling you to stop overcomplicating things. Unlike Rework, which felt like a manifesto for its own sake, Getting Real actually delivers practical advice.

The book is structured in short, punchy sections — Organization, Code, Process, Feature Selection — each filled with actionable tips. Build less. Ship sooner. Say no to features. Get something real in front of users fast. The advice draws heavily from agile, Scrum, Lean, and Kanban methodologies.

That's both the strength and the weakness.

If you already know agile principles, this book is a great reinforcement. Each tip hits like a well-timed reminder of what you already know but keep forgetting. Ship the simplest thing. Reduce scope before extending deadlines. Meetings are toxic. These aren't new ideas, but Fried articulates them with clarity.

If you don't know agile, you might misapply the advice. "Build less" without context sounds like "cut corners." "Say no to features" without understanding trade-offs sounds like laziness. The book assumes a level of product and engineering maturity that not every reader will have.

The writing is tight. No wasted pages. You can read it in an afternoon. That's by design — Fried practices what he preaches.

Where I push back: the book is heavily biased toward small teams building web apps. The advice doesn't scale cleanly to large organizations, complex systems, or regulated industries. If you're running a platform with millions of users and compliance requirements, "just ship it" isn't always an option.

Still — if I ran a team, I'd give everyone a copy. The core philosophy is right: simplicity wins. Build what matters. Cut what doesn't. Ship and iterate.