Quotessence
Home / Authors / Joel Spolsky Books
Joel Spolsky

Joel Spolsky Books

Software Engineer

Related Quotes

“Many rookie software managers think that they can "motivate" their programmers to work faster by giving them nice, "tight" (unrealistically short) schedules. I think this kind of motivation is brain-dead. When I'm behind schedule, I feel doomed and depressed and unmotivated. When I'm working ahead of schedule, I'm cheerful and productive. The schedule is not the place to play psychological games.”

DevelopmentSoftwareMotivateProject ManagementSchedule
Book:Joel on Software
Create image

“The Joel Test 1. Do you use source control? 2. Can you make a build in one step? 3. Do you make daily builds? 4. Do you have a bug database? 5. Do you fix bugs before writing new code? 6. Do you have an up-to-date schedule? 7. Do you have a spec? 8. Do programmers have quiet working conditions? 9. Do you use the best tools money can buy? 10. Do you have testers? 11. Do new candidates write code during their interview? 12. Do you do hallway usability testing?”

OfficeSoftwareTestingCodingTestSoftware DevelopmentUsability
Book:Joel on Software
Create image

“The confidence you get from knowing about every crash, anywhere in the world, is crucial to delivering a high-quality product that needs to be used in the wild. In the consumer software business, you can't rely on your customers to tell you about crashes—many of them may not be technical enough, and most of them won't bother to take time off of their own important work to give you a useful crash report unless you make it completely automatic.”

CustomersSoftwareUsersCrashBug
Book:Joel on Software
Create image

“We're programmers. Programmers are, in their hearts, architects, and the first thing they want to do when they get to a site is to bulldoze the place flat and build something grand. We're not excited by incremental renovation: tinkering, improving, planting flower beds. There's a subtle reason why programmers always want to throw away the code and start over. The reason is that they think the old code is a mess. And here is the interesting observation: They are probably wrong. The reason that they think the old code is a mess is because of a cardinal, fundamental law of programming: It's harder to read code than to write it.”

CodeProgrammersRewrite
Book:Joel on Software
Create image

“Usability, fundamentally, is a matter of bringing a bit of human rights into the world of computer-human interaction. It's a way to let our ideals shine through in our software, no matter how mundane the software is. You may think that you're stuck in a boring, drab IT department making mind-numbing inventory software that only five lonely people will ever use. But you have daily opportunities to show respect for humanity even with the most mundane software.”

Usability
Book:User Interface Design for Programmers
Create image

“Software development takes immense intellectual effort. Even the best programmers can rarely sustain that level of effort for more than a few hours a day. Beyond that, they need to rest their brains a bit, which is why they always seem to be surfing the Internet or playing games when you barge in on them.”

NeedsSeemsGamesBitsHoursLevelsEffortBrainDevelopmentInternetIntellectualSoftwareImmenseSurfingProgrammersPlaying GamesSoftware DevelopmentBargesSurfing The Internet
Author:Joel Spolsky
Create image

“Not having a schedule is OK if it's your PhD and you plan to spend 14 years on the thing, or if you're a programmer working on the next Duke Nukem and we'll ship when we're good and ready. But for almost any kind of real business, you just have to know how long things are going to take, because developing a product costs money.”

IfsKnowsYearsKindLongRealNextKnow HowPlansReadyProductsCostShipsDevelopingProgrammingSchedulesProgrammersDukesPhds
Author:Joel Spolsky
Create image

“There's a subtle reason that programmers always want to throw away the code and start over. The reason is that they think the old code is a mess. [...] The reason that they think the old code is a mess is because of a cardinal, fundamental law of programming: It's harder to read code than to write it.”

ThinkingWantWritingReasonLawDesignHarderFundamentalsMessCodeProgrammingSubtleStarting OverProgrammersCardinals
Book:Joel on Software
Create image

“Usability is not everything. If usability engineers designed a nightclub, it would be clean, quiet, brightly lit, with lots of places to sit down, plenty of bartenders, menus written in 18-point sans-serif, and easy-to-find bathrooms. But nobody would be there. They would all be down the street at Coyote Ugly pouring beer on each other.”

IfsWould BeEasyWrittenStreetsQuietCleanUglyPlentyBeerEngineersBathroomLitPouringMenusNightclubsBartenderCoyotesUsabilityCoyote Ugly
Author:Joel Spolsky
Create image