Joel on Software: And on Diverse and Occasionally Related Matters That Will Prove of Interest to Software Developers, Designers, and Managers, and to Those Who, Whether by Good Fortune or Ill Luck, Work with Them in Some Capacity

  • 5h 48m
  • Joel Spolsky
  • Apress
  • 2004

Joel Spolsky began his legendary web log, joelonsoftware.com, in March 2000, in order to offer insights for improving the world of programming. Spolsky based these observations on years of personal experience.

The result just a handful of years later? Spolsky's technical knowledge, caustic wit, and extraordinary writing skills have earned him status as a programming guru! His blog has become renowned throughout the programming world now linked to more than six hundred websites and translated into over thirty languages.

Joel on Software covers every conceivable aspect of software programming from the best way to write code, to the best way to design an office in which to write code! All programmers, all people who want to enhance their knowledge of programmers, and all who are trying to manage programmers will surely relate to Joel's musings.

About the Author

Joel Spolsky is a globally recognized expert on the software development process. His web site Joel on Software joelonsoftware.com) is popular with software developers around the world and has been translated into over 30 languages. As the founder of Fog Creek Software in New York City, he created FogBugz, a popular project management system for software teams. Joel has worked at Microsoft, where he designed Visual Basic for Applications as a member of the Excel team, and at Juno Online Services, developing an Internet client used by millions. He has written two books: User Interface Design for Programmers (Apress, 2001) and Joel on Software (Apress, 2004). Joel holds a bachelor's of science degree in computer science from Yale University. Before college, he served in the Israeli Defense Forces as a paratrooper, and he was one of the founders of Kibbutz Hanaton.

In this Book

  • Choosing a Language
  • Back to Basics
  • The Joel Test: 12 Steps to Better Code
  • The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!)
  • Painless Functional Specifications—Part 1: Why Bother?
  • Painless Functional Specifications—Part 2: What's a Spec?
  • Painless Functional Specifications—Part 3: But… How?
  • Painless Functional Specifications—Part 4: Tips
  • Painless Software Schedules
  • Daily Builds are Your Friend
  • Hard-Assed Bug Fixin'
  • Five Worlds
  • Paper Prototyping
  • Don't Let Architecture Astronauts Scare You
  • Fire and Motion
  • Craftsmanship
  • Three Wrong Ideas from Computer Science
  • Biculturalism
  • Get Crash Reports From Users—Automatically!
  • The Guerilla Guide to Interviewing
  • Incentive Pay Considered Harmful
  • Top Five (Wrong) Reasons You Don't Have Testers
  • Human Task Switches Considered Harmful
  • Things You Should Never Do, Part One
  • The Iceberg Secret, Revealed
  • The Law of Leaky Abstractions
  • Lord Palmerston on Programming
  • Measurement
  • Rick Chapman is in Search of Stupidity
  • What is the Work of Dogs in This Country?
  • Getting Things Done When You're Only a Grunt
  • Two Stories
  • Big Macs vs. the Naked Chef
  • Nothing is as Simple as it Seems
  • In Defense of Not-Invented-Here Syndrome
  • Strategy Letter I: Ben & Jerry's vs. Amazon
  • Strategy Letter II: Chicken-and-Egg Problems
  • Strategy Letter III: Let Me Go Back!
  • Strategy Letter IV: Bloatware and the 80/20 Myth
  • Strategy Letter V: The Economics of Open Source
  • A Week of Murphy's Law Gone Wild
  • How Microsoft Lost the API War
  • Microsoft Goes Bonkers
  • Our .NET Strategy
  • Please Sir May I Have a Linker?
SHOW MORE
FREE ACCESS