Spolsky The Best Software Writing I

Selected and Introduced by Joel Spolsky
1. ed
ISBN: 978-1-4302-0038-3
Verlag: Apress
Format: PDF
Kopierschutz: 1 - PDF Watermark

E-Book, Englisch, 328 Seiten

* Will appeal to the same (large) audience as Joel on Software * Contains exclusive commentary by Joel * Lots of free publicity both because of Joel's influence in the community and the influence of the contributors

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.

Autoren/Hrsg.

Spolsky, Avram Joel

Inhaltsverzeichnis

1;CONTENTS;6
2;ABOUT THE EDITOR;8
3;ABOUT THE AUTHORS;10
4;INTRODUCTION;16
5;STYLE IS SUBSTANCE --- Ken Arnold;20
6;AWARD FOR THE SILLIEST USER INTERFACE: WINDOWS SEARCH --- Leon Bambrick;26
6.1;So You’d Like to Search for Something!;27
7;THE PITFALLS OF OUTSOURCING PROGRAMMERS --- Michael Bean;28
7.1;Why Some Software Companies Confuse the Box with the Chocolates;31
7.2;Design and Assembly Are Different;32
8;EXCEL AS A DATABASE --- Rory Blyth;36
9;ICSOC04 TALK --- Adam Bosworth;42
10;AUTISTIC SOCIAL SOFTWARE --- Danah Boyd;54
10.1;Sociable Media, Sci-Fi, and Mental Illness;55
10.2;Autism and Attention Deficit Disorder;57
10.3;Socially Inept Computers;58
10.4;Friendster’s Success;60
10.5;Situating Technology in Practice;62
11;WHY NOT JUST BLOCK THE APPS THAT RELY ON UNDOCUMENTED BEHAVIOR? --- Raymond Chen;66
12;KICKING THE LLAMA --- Kevin Cheng and Tom Chi;70
13;SAVE CANADA’S INTERNET FROM WIPO --- Cory Doctorow;72
14;EA: THE HUMAN STORY --- ea_spouse;78
15;STRONG TYPING VS. STRONG TESTING --- Bruce Eckel;86
15.1;If it’s not tested, it’s broken.;94
15.2;Strong testing, not strong typing.;95
16;PROCESSING PROCESSING --- Paul Ford;98
17;GREAT HACKERS --- Paul Graham;114
17.1;Edisons;115
17.2;More than Money;116
17.3;The Final Frontier;119
17.4;Interesting;120
17.5;Nasty Little Problems;122
17.6;Clumping;123
17.7;Recognition;125
17.8;Cultivation;126
18;THE LOCATION FIELD IS THE NEW COMMAND LINE --- John Gruber;130
18.1;Who Loses As Web Apps Win?;134
19;STARBUCKS DOES NOT USE TWO-PHASE COMMIT --- Gregor Hohpe ;138
19.1;Hotto Cocoa o Kudasai;139
19.2;Correlation;140
19.3;Exception Handling;140
19.4;Conversations;142
19.5;Real Life Architecture;143
20;PASSION --- Ron Jeffries;144
20.1;Grampa Speaks;145
20.2;Born for Passion;146
21;C++—THE FORGOTTEN TROJAN HORSE --- Eric Johnson ;148
22;HOW MANY MICROSOFT EMPLOYEES DOES IT TAKE TO CHANGE A LIGHTBULB? --- Eric Lippert;154
23;WHAT TO DO WHEN YOU’RE SCREWED --- Michael “Rands” Lopp;158
23.1;5 Scenarios for High-Velocity Engineering Managers;158
23.1.1;#1) I’m Missing a Document and People Are Yelling at Me;160
23.1.2;#2) A Significant Development Tool Does Not Exist on My Team;162
23.1.3;#3) I Can’t Stand My Product/Program Manager or They Plain Don’t Exist;163
23.1.4;#4) My Product Is Nowhere Near Done;164
23.1.5;#5) My Company/Job Sucks or Is About to Suck;166
24;LARRY’S RULES OF SOFTWARE ENGINEERING #2: MEASURING TESTERS BY TEST METRICS DOESN’T --- Larry Osterman;170
25;TEAM COMPENSATION --- Mary Poppendieck;176
25.1;The Morning After;177
25.2;The Aftershocks;178
25.2.1;Dysfunction #1: Competition;179
25.2.2;Dysfunction #2: The Perception of Unfairness;180
25.2.3;Dysfunction #3: The Perception of Impossibility;180
25.2.4;Dysfunction #4: Suboptimization;181
25.2.5;Dysfunction #5: Destroying Intrinsic Motivation;182
25.3;One Week Later;182
25.3.1;Guideline #1: Make Sure the Promotion System Is Unassailable;184
25.3.2;Guideline #2: De-emphasize the Merit Pay System;185
25.3.3;Guideline #3: Tie Profit Sharing to Economic Drivers;186
25.3.4;Guideline # 4: Reward Based on Span of Influence, Not Span of Control;187
25.3.5;Guideline #5: Find Better Motivators than Money;188
25.4;Six Months Later;188
26;MAC WORD 6.0 --- Rick Schaut;190
26.1;Mac Word 5 and Pyramid;192
26.2;Exit Jeff Raikes, Enter Chris Peters;193
26.3;Technical Hurdles;194
26.4;Technical Achievement;196
26.5;Learning the Meaning of “Mac-Like”;198
27;A GROUP IS ITS OWN WORST ENEMY --- Clay Shirky;202
27.1;Part One: How Is a Group Its Own Worst Enemy?;206
27.2;Part Two: Why Now?;213
27.3;Part Three: What Can We Take for Granted?;218
27.3.1;Three Things to Accept;219
27.3.2;Four Things to Design For;222
27.4;Conclusion;227
28;GROUP AS USER: FLAMING AND THE DESIGN OF SOCIAL SOFTWARE --- Clay Shirky;230
28.1;Learning from Flame Wars;231
28.2;Netiquette and Kill Files;233
28.3;The Tragedy of the Conversational Commons;234
28.4;Weblog and Wiki Responses;235
28.5;Reviving Old Tools;236
28.6;Novel Operations on Social Facts;237
28.7;Rapid, Iterative Experimentation;239
29;CLOSING THE GAP, PART 1 --- Eric Sink;242
29.1;Proactive Sales;243
29.1.1;#ifdef apology;244
29.1.2;#endif;244
29.2;Working with a Sales Guy;245
29.3;Characteristics of a Sales Guy;245
29.4;One More Mandatory Trait for a Sales Guy;247
29.5;Reasons to Have a Sales Guy;248
29.5.1;Reason #1: Nobody Really Wants Your Product;248
29.5.2;Reason #2: Your Product Is Very Expensive;248
29.5.3;Reason #3: Your Product Is No Longer Being Improved;249
29.6;The “No Sales Guy” Approach;249
29.7;The Bottom Line;250
30;CLOSING THE GAP, PART 2 --- Eric Sink;251
30.1;Responsive Sales;252
30.2;1. Make Sure Customers Know About Your Product;253
30.2.1;Be Careful with Advertising;253
30.2.2;Try a Tradeshow;254
30.2.3;Develop “in the Open”;254
30.3;2. Make Sure Your Product Is Something Customers Want;255
30.3.1;Choose Your Position;255
30.3.2;Choose Your Competition;255
30.3.3;Develop “in the Open”;256
30.4;3. Make Sure They Can Afford Your Product;256
30.5;Further Reading;257
30.6;4. Offer a Full-Featured Demo Download;258
30.6.1;Make the Download Easy to Find;259
30.6.2;Make the Download Full-Featured;259
30.6.3;Polish Your Installer;259
30.6.4;Let the Customer Remain Anonymous;259
30.7;5. Answer the Customers’ Questions;259
30.8;6. Provide a Place for Community;260
30.9;7. Make It Easy to Buy Over the Web;261
30.9.1;Don’t Make Customers Log In;261
30.9.2;You Don’t Need a Shopping Cart;262
30.9.3;Give Customers the Product Right Away;262
30.10;But We Can’t Do It This Way!;263
30.11;We’re Not Perfect;263
31;HAZARDS OF HIRING --- Eric Sink;264
31.1;1. Hire After the Need, Not Before;265
31.2;2. Realize That Hiring Is All About Probabilities;266
31.3;3. Know the Law;267
31.4;4. Get a Variety of Opinions;268
31.5;Hiring Programmers: The Usual Advice;269
31.6;Look for Self-Awareness;270
31.7;Hire Developers, Not Programmers;271
31.8;Education Is Good;272
31.9;But Too Much Education Is a Yellow Light;273
31.10;Look at the Code;274
31.11;The Very Best;276
32;POWERPOINT REMIX --- Aaron Swartz ;279
33;A QUICK (AND HOPEFULLY PAINLESS) RIDE THROUGH RUBY (WITH CARTOON FOXES) --- why the lucky stiff;285
33.1;Language and I Mean Language;287
33.2;The Parts of Speech;291
33.2.1;Variables;292
33.2.2;Numbers;293
33.2.3;Strings;293
33.2.4;Symbols;294
33.2.5;Constants;294
33.2.6;Methods;295
33.2.7;Method Arguments;296
33.2.8;Class Methods;296
33.2.9;Global Variables;297
33.2.10;Instance Variables;297
33.2.11;Class Variables;298
33.2.12;Blocks;298
33.2.13;Block Arguments;299
33.2.14;Ranges;300
33.2.15;Arrays;300
33.2.16;Hashes;301
33.2.17;Regular Expressions;302
33.2.18;Operators;302
33.2.19;Keywords;303
33.3;If I Haven’t Treated You Like a Child Enough Already;304
33.4;An Example to Help You Grow Up;306
33.5;And So, the Quick Trip Came to an Eased, Cushioned Halt;308
34;INDEX;311
35;COLOPHON;324