MORE JOEL ON SOFTWARE Further Thoughts 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 Joel Spolsky More Joel on Software: Further Thoughts 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 withThem in Some Capacity Copyright © 2008 by Joel Spolsky All rights reserved. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without the prior written permission of the copyright owner and the publisher. ISBN-13 (paperback): 978-1-4302-0987-4 ISBN-13 (electronic): 978-1-4302-0988-1 Printed and bound in the United States of America 9 8 7 6 5 4 3 2 1 Trademarked names may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, we use the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. Lead Editor: Jeffrey Pepper Editorial Board: Clay Andres, Steve Anglin, Ewan Buckingham, Tony Campbell, Gary Cornell, Jonathan Gennick, Matthew Moodie, Joseph Ottinger,Jeffrey Pepper,Frank Pohlmann, BenRenow-Clarke, Dominic Shakeshaft, Matt Wade, Tom Welsh Associate Publisher | Project Manager: Grace Wong Senior Copy Editor: Ami Knox Associate Production Director: Kari Brooks-Copony Production Manager: Kelly Winquist Compositor: Dina Quan Proofreader: April Eddy Indexer: Broccoli Information Management Artist: April Milne Cover Designer: KurtKrames Manufacturing Director: Tom Debolski Distributed to the book trade worldwide by Springer-Verlag New York, Inc., 233 Spring Street, 6th Floor, New York, NY 10013. Phone 1-800-SPRINGER, fax 201-348-4505, e-mail [email protected],or visit http://www.springeronline.com. For information on translations, please contact Apress directly at 2855 Telegraph Avenue, Suite 600, Berkeley,CA 94705. Phone 510-549-5930, fax 510-549-5939, e-mail [email protected],or visit http://www.apress.com. Apress and friends of ED books may be purchased in bulk for academic, corporate, or promotional use. eBook versions and licenses are also available for most titles. For more information, reference our Special Bulk Sales–eBook Licensing web page at http://www.apress.com/info/bulksales. The information in this book is distributed on an “as is” basis, without warranty. Although every precaution has been taken in the preparation of this work, neither the author(s) nor Apress shall have any liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly or indirectly by the information contained in this work. For Jared, CONTENTS Joel, Apress, Blogs, and Blooks . . . . . . . . . . . . . ix About the Author. . . . . . . . . . . . . . . . . . . . xiii part one Managing People . . . . . . . . . . . . . . . . . . 1 one My First BillG Review. . . . . . . . . . . . . . . . . . 3 two Finding Great Developers . . . . . . . . . . . . . . . 9 three AField Guide to Developers . . . . . . . . . . . . . 21 four Three Management Methods (Introduction) . . . 35 five The Command and Control Management Method . . . . . . . . . . . . . . . . . . . . . . . . 37 six The Econ 101 Management Method . . . . . . . . 41 seven The Identity Management Method . . . . . . . . . 47 part two Advice to Potential Programmers. . . . . . . 51 eight The Perils of JavaSchools. . . . . . . . . . . . . . . 53 nine Talk at Yale . . . . . . . . . . . . . . . . . . . . . . 59 ten Advice for Computer Science College Students . . . . . . . . . . . . . . . . . . . . . . . . 73 part three The Impact of Design . . . . . . . . . . . . . . 83 eleven Font Smoothing, Anti-Aliasing, and Subpixel Rendering . . . . . . . . . . . . . . . . . . . . . . . 85 twelve AGame of Inches. . . . . . . . . . . . . . . . . . . 89 vi Contents thirteen The Big Picture . . . . . . . . . . . . . . . . . . . . 93 fourteen Choices = Headaches. . . . . . . . . . . . . . . . . 99 fifteen It’s Not Just Usability . . . . . . . . . . . . . . . . 103 sixteen Building Communities with Software . . . . . . . 111 part four Managing Large Projects. . . . . . . . . . . . 123 seventeen Martian Headsets . . . . . . . . . . . . . . . . . . 125 eighteen Why Are the Microsoft Office File Formats So Complicated? (And Some Workarounds) . . . . 143 nineteen Where There’s Muck, There’s Brass . . . . . . . . 151 part five Programming Advice . . . . . . . . . . . . . . 155 twenty Evidence-Based Scheduling. . . . . . . . . . . . . 157 twenty-one Strategy Letter VI . . . . . . . . . . . . . . . . . . 171 twenty-two Can Your Programming Language Do This? . . . 177 twenty-three Making Wrong Code Look Wrong. . . . . . . . . 183 part six Starting a Software Business . . . . . . . . . 201 twenty-four Foreword to Eric Sink on the Business of Software . . . . . . . . . . . . . . . . . . 203 twenty-five Foreword to Micro-ISV: From Vision to Reality . . . . . . . . . . . . . . . . . . . . . . . 207 twenty-six Hitting the High Notes . . . . . . . . . . . . . . . 211 part seven Running a Software Business. . . . . . . . . 221 twenty-seven Bionic Office. . . . . . . . . . . . . . . . . . . . . 223 twenty-eight Up the Tata Without a Tutu . . . . . . . . . . . . 227 twenty-nine Simplicity. . . . . . . . . . . . . . . . . . . . . . . 231 Contents vii thirty Rub a Dub Dub . . . . . . . . . . . . . . . . . . . 235 thirty-one Top Twelve Tips for Running a Beta Test . . . . . 241 thirty-two Seven Steps to Remarkable Customer Service . . 245 part eight Releasing Software. . . . . . . . . . . . . . . . 255 thirty-three Picking a Ship Date . . . . . . . . . . . . . . . . . 257 thirty-four Camels and Rubber Duckies . . . . . . . . . . . . 263 part nine Revising Software . . . . . . . . . . . . . . . . 281 thirty-five Five Whys. . . . . . . . . . . . . . . . . . . . . . . 283 thirty-six Set Your Priorities . . . . . . . . . . . . . . . . . . 289 Index . . . . . . . . . . . . . . . . . . . . . . . . . 297 JOEL, APRESS, BLOGS, AND BLOOKS “A long time ago in a galaxy far,far away . . .” Well, actually it was late in 2000, during Apress’s first full year of operation. We were a tiny little computer book publisher then, with little name recognition, and we planned to publish only a handful of books that year—roughly as many books for that whole year as Apress now publishes in a single month. Iwas learning the hard way about how to be a publisher and proba- bly spending way too much time looking at web sites and programming than I should have in response to that. Anyway, one day I came across this web site called Joel on Software,which was run by a guy with strong opinions and an unusual, clever writing style, along with a willingness to take on the conventional wisdom. In particular, he was writing this ongoing series about how bad most user interfaces were—mostly because programmers by and large knew,as Joel and I would say,using the same Yiddish-derived NYC vernacular that we both share, “bupkis” about what users really want. And I, like many, was hooked both by the series and the occasional random essay that Joel wrote. And then I had this epiphany: I’m a publisher,Ilike reading his stuff, why not turnit into a book? I wrote Joel, introduced myself, and though he was initially skeptical, I somehow convinced him that if he would turn the user interface essays into a book, people would buy tons of them and he and I would make lots and lots of money. (Of course, this was long before FogBugz became the success it is and Joel started to command serious dollars as a coveted speaker—but then we were both younger and, yes, a whole lot poorer in those days.) Anyway, Joel added some new content to make the book more appealing and, I thought, moremarketable, and suddenly,Apress had to figure out how to publish its first full-color book. The result, User Interface Design for Programmers,officially appeared on June 21, 2001, x Joel,Apress,Blogs,and Blooks and is now acknowledged as the first “blook” ever. Somewhat shock- ingly to the computer book industry and me, it became a runaway best seller by the standard of the times. By the way, it is still in print, still sell- ing very well, and still worth reading. (Although, speaking as your publisher and not as your friend, Joel, how ’bout that revision?) Anyway, some would (now) argue that User Interface Design for Programmers isn’t a pure blook because the addition of “too much” new material that was not on Joel’s web site makes it a hybrid—as I sup- pose befits its pioneering status. But a few years later, Joel on Software was the most popular blog for programmers in the world because Joel of course had kept on writing these amazingly interesting essays—perhaps the most famous being the classic “How Microsoft Lost the API War,” which I know literally turned parts of Microsoft’s development upside down. And then I had yet another epiphany: let’s collect the best of these essays and publish them with no substantial new content other than an occasional foreword where Joel thought it appropriate. And even though 98 percent of the material in the book that became Joel on Softwarewas available on the Web, and people thought Apress was nuts for publishing it in late 2004, the book has gone through ten printings and remains a best-selling book today. Because, it still seems, when it comes to digesting the chocolate truffle that is the typical Joel essay, print is still more pleasurable for many than a browser. But Joel hasn’tstopped thinking hardabout what it takes to program well or hire good programmers, nor has he stopped challenging the con- ventional wisdom with his insights. So I convinced him the time was right for a sequel that collected the “best of Joel” published since the first Joelcame out in late 2004. And so you have in your hands the second collection of Joel’s insights, occasional random thoughts, and yes, occasional rants—all encased in the sparkling prose that Joel is known for. And even though nothing has been done to his writing save for some minor copy editing, you do have the latest “best of Joel” in a very high-contrast form com- pared to your screen or even your Kindle, known now as a “blook.” (And Joel, I obviously hope you will enjoy them as much as you did the ones in the first collection.) Joel,Apress,Blogs,and Blooks xi This book, like the first, has a somewhat unusual cover and subtitle. This is because Joel and I are both bibliophiles (OK, Joel is a bibliophile; I’m a bibliomaniac) and we are both very fond of the kind of thing the classic book printers of the 17th and 18th centuries did to liven up their books—and their titles. In the case of the first Joel on Software covers, we paid homage to Burton’s Anatomy of Melancholy;here we pay hom- age to Hobbes’s The Leviathan and the famous frontispiece where the giant is made up of lots of individuals, because both Joel and I felt this was not a bad metaphor for how programming is done: individuals building something gigantic—but individuals are the key. Finally, on a more personal note: In spite of his now substantial fame, Joel remains a down-to-earth kind of guy, or again in our common ver- nacular,atrue mensch and someone I am proud to have as a close friend. Gary Cornell Cofounder, Apress