Joel on Software

**Author:** Joel Spolsky **Estimated Reading Time:** 4 hours 20 minutes

**What You'll Learn:** - Why software quality depends on testing, talent, and clear specifications - How to design user interfaces that people can actually use - What makes great software teams tick - How strategic thinking shapes technology decisions - Why the simplest solution is usually the right one

**Who This Book Is For:** Software developers who want to understand the craft beyond code. Project managers responsible for shipping products. Entrepreneurs building technology companies. Anyone who has ever wondered why some software delights users while other software makes them want to throw their computer out a window.

In the late 1990s, a young programmer named Joel Spolsky started writing essays on the internet. He had worked at Microsoft on the Excel team, where he learned how large organizations build software. He had watched brilliant projects succeed and equally brilliant projects fail. He had observed the strange rituals of software development, the unspoken rules that separated great teams from mediocre ones, and the countless ways that smart people make dumb decisions when technology meets business. Those essays became a blog called Joel on Software. The blog became required reading for programmers around the world. And eventually, the best essays became this book. The software industry in the late 1990s and early 2000s was a strange place. The dot-com boom was in full swing. Companies were spending millions of dollars on websites that did nothing. Programmers were treated like interchangeable parts, hired in bulk and fired in bulk. Software was shipped full of bugs because nobody had time to test it. User interfaces were designed by engineers who thought that if they could figure out how to use a feature, everyone else could too. Spolsky looked at this chaos and started asking simple questions. Why do some software teams produce great work while others produce garbage? Why do users hate software that engineers think is perfectly fine? Why do companies make technology decisions that seem obviously wrong in hindsight? His answers were refreshingly direct. Software quality comes from disciplined testing and dedicated testers. Great products come from hiring great people and giving them room to work. User interfaces need to be tested with real users, not imagined users. Specifications need to be written before code, not after. And companies need to think strategically about what they build, what they buy, and what they give away. What makes Spolsky's writing endure is that he never lost sight of the human element. Software is built by people, for people. The best tools, the best processes, and the best strategies all serve one purpose: helping smart people work together to create something useful. When we…