| CONTENTS | 6 |
|---|
| ABOUT THE EDITOR | 8 |
|---|
| ABOUT THE AUTHORS | 10 |
|---|
| INTRODUCTION | 16 |
|---|
| STYLE IS SUBSTANCE --- Ken Arnold | 20 |
|---|
| AWARD FOR THE SILLIEST USER INTERFACE: WINDOWS SEARCH --- Leon Bambrick | 26 |
|---|
| So You’d Like to Search for Something! | 27 |
| THE PITFALLS OF OUTSOURCING PROGRAMMERS --- Michael Bean | 28 |
|---|
| Why Some Software Companies Confuse the Box with the Chocolates | 31 |
| Design and Assembly Are Different | 32 |
| EXCEL AS A DATABASE --- Rory Blyth | 36 |
|---|
| ICSOC04 TALK --- Adam Bosworth | 42 |
|---|
| AUTISTIC SOCIAL SOFTWARE --- Danah Boyd | 54 |
|---|
| Sociable Media, Sci-Fi, and Mental Illness | 55 |
| Autism and Attention Deficit Disorder | 57 |
| Socially Inept Computers | 58 |
| Friendster’s Success | 60 |
| Situating Technology in Practice | 62 |
| WHY NOT JUST BLOCK THE APPS THAT RELY ON UNDOCUMENTED BEHAVIOR? --- Raymond Chen | 66 |
|---|
| KICKING THE LLAMA --- Kevin Cheng and Tom Chi | 70 |
|---|
| SAVE CANADA’S INTERNET FROM WIPO --- Cory Doctorow | 72 |
|---|
| EA: THE HUMAN STORY --- ea_spouse | 78 |
|---|
| STRONG TYPING VS. STRONG TESTING --- Bruce Eckel | 86 |
|---|
| If it’s not tested, it’s broken. | 94 |
| Strong testing, not strong typing. | 95 |
| PROCESSING PROCESSING --- Paul Ford | 98 |
|---|
| GREAT HACKERS --- Paul Graham | 114 |
|---|
| Edisons | 115 |
| More than Money | 116 |
| The Final Frontier | 119 |
| Interesting | 120 |
| Nasty Little Problems | 122 |
| Clumping | 123 |
| Recognition | 125 |
| Cultivation | 126 |
| THE LOCATION FIELD IS THE NEW COMMAND LINE --- John Gruber | 130 |
|---|
| Who Loses As Web Apps Win? | 134 |
| STARBUCKS DOES NOT USE TWO-PHASE COMMIT --- Gregor Hohpe | 138 |
|---|
| Hotto Cocoa o Kudasai | 139 |
| Correlation | 140 |
| Exception Handling | 140 |
| Conversations | 142 |
| Real Life Architecture | 143 |
| PASSION --- Ron Jeffries | 144 |
|---|
| Grampa Speaks | 145 |
| Born for Passion | 146 |
| C++—THE FORGOTTEN TROJAN HORSE --- Eric Johnson | 148 |
|---|
| HOW MANY MICROSOFT EMPLOYEES DOES IT TAKE TO CHANGE A LIGHTBULB? --- Eric Lippert | 154 |
|---|
| WHAT TO DO WHEN YOU’RE SCREWED --- Michael “Rands” Lopp | 158 |
|---|
| 5 Scenarios for High-Velocity Engineering Managers | 158 |
| #1) I’m Missing a Document and People Are Yelling at Me | 160 |
| #2) A Significant Development Tool Does Not Exist on My Team | 162 |
| #3) I Can’t Stand My Product/Program Manager or They Plain Don’t Exist | 163 |
| #4) My Product Is Nowhere Near Done | 164 |
| #5) My Company/Job Sucks or Is About to Suck | 166 |
| LARRY’S RULES OF SOFTWARE ENGINEERING #2: MEASURING TESTERS BY TEST METRICS DOESN’T --- Larry Osterman | 170 |
|---|
| TEAM COMPENSATION --- Mary Poppendieck | 176 |
|---|
| The Morning After | 177 |
| The Aftershocks | 178 |
| Dysfunction #1: Competition | 179 |
| Dysfunction #2: The Perception of Unfairness | 180 |
| Dysfunction #3: The Perception of Impossibility | 180 |
| Dysfunction #4: Suboptimization | 181 |
| Dysfunction #5: Destroying Intrinsic Motivation | 182 |
| One Week Later | 182 |
| Guideline #1: Make Sure the Promotion System Is Unassailable | 184 |
| Guideline #2: De-emphasize the Merit Pay System | 185 |
| Guideline #3: Tie Profit Sharing to Economic Drivers | 186 |
| Guideline # 4: Reward Based on Span of Influence, Not Span of Control | 187 |
| Guideline #5: Find Better Motivators than Money | 188 |
| Six Months Later | 188 |
| MAC WORD 6.0 --- Rick Schaut | 190 |
|---|
| Mac Word 5 and Pyramid | 192 |
| Exit Jeff Raikes, Enter Chris Peters | 193 |
| Technical Hurdles | 194 |
| Technical Achievement | 196 |
| Learning the Meaning of “Mac-Like” | 198 |
| A GROUP IS ITS OWN WORST ENEMY --- Clay Shirky | 202 |
|---|
| Part One: How Is a Group Its Own Worst Enemy? | 206 |
| Part Two: Why Now? | 213 |
| Part Three: What Can We Take for Granted? | 218 |
| Three Things to Accept | 219 |
| Four Things to Design For | 222 |
| Conclusion | 227 |
| GROUP AS USER: FLAMING AND THE DESIGN OF SOCIAL SOFTWARE --- Clay Shirky | 230 |
|---|
| Learning from Flame Wars | 231 |
| Netiquette and Kill Files | 233 |
| The Tragedy of the Conversational Commons | 234 |
| Weblog and Wiki Responses | 235 |
| Reviving Old Tools | 236 |
| Novel Operations on Social Facts | 237 |
| Rapid, Iterative Experimentation | 239 |
| CLOSING THE GAP, PART 1 --- Eric Sink | 242 |
|---|
| Proactive Sales | 243 |
| #ifdef apology | 244 |
| #endif | 244 |
| Working with a Sales Guy | 245 |
| Characteristics of a Sales Guy | 245 |
| One More Mandatory Trait for a Sales Guy | 247 |
| Reasons to Have a Sales Guy | 248 |
| Reason #1: Nobody Really Wants Your Product | 248 |
| Reason #2: Your Product Is Very Expensive | 248 |
| Reason #3: Your Product Is No Longer Being Improved | 249 |
| The “No Sales Guy” Approach | 249 |
| The Bottom L
|
