I. M. Wright's ""Hard Code""
Get the brutal truth about coding, testing, and project management-from a Microsoft insider who tells it like it is. I. M. Wright's deliberately provocative column ""Hard Code"" has been sparking debate amongst thousands of engineers at Microsoft for years. And now (despite...
| Autor principal: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Sebastopol :
Microsoft Press
2011.
|
| Edición: | 2nd ed |
| Colección: | Developer Best Practices
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009628298306719 |
Tabla de Contenidos:
- Reader Acclaim for I. M. Wright's "Hard Code" Column; Contents at a Glance; Table of Contents; Foreword; Foreword to the First Edition; Introduction; How This Book Happened; Who Should Read This Book; Organization of This Book; How Microsoft Is Organized; Sample Tools and Documents; System Requirements; Errata & Book Support; We Want to Hear from You; Stay in Touch; Chapter 1: Project Mismanagement; June 1, 2001: "Dev schedules, flying pigs, and other fantasies"; October 1, 2001: "Pushing the envelopes: Continued contention over dev schedules"
- May 1, 2002: "Are we having fun yet? The joy of triage."December 1, 2004: "Marching to death"; October 1, 2005: "To tell the truth"; September 1, 2008: "I would estimate"; May 1, 2009: "It starts with shipping"; September 1, 2009: "Right on schedule"; May 1, 2010: "Coordinated agility"; Chapter 2: Process Improvement, Sans Magic; September 2, 2002: "Six Sigma? Oh please!"; October 1, 2004: "Lean: More than good pastrami"; April 1, 2005: "Customer dissatisfaction"; March 1, 2006: "The Agile bullet"; October 1, 2007: "How do you measure yourself?"; October 1, 2010: "You can depend on me"
- November 1, 2010: "Am I bugging you? Bug Reports"December 1, 2010: "There's no place like production"; February 1, 2011: "Cycle time-The soothsayer of productivity"; Chapter 3: Inefficiency Eradicated; July 1, 2001: "Late specs: Fact of life or genetic defect?"; June 1, 2002: "Idle hands"; June 1, 2004: "The day we met"; July 1, 2006: "Stop writing specs, co-located feature crews"; February 1, 2007: "Bad specs: Who is to blame?"; February 1, 2008: "So far away-Distributed development"; December 1, 2008: "De-optimization"; April 1, 2009: "Your World. Easier"
- April 1, 2011: "You have to make a decision"Chapter 4: Cross Disciplines; April 1, 2002: "The modern odd couple? Dev and Test"; July 1, 2004: "Feeling testy-The role of testers"; May 1, 2005: "Fuzzy logic-The liberal arts"; November 1, 2005: "Undisciplined-What's so special about specialization?"; January 1, 2009: "Sustained engineering idiocy"; May 1, 2011: "Test don't get no respect"; Chapter 5: Software Quality-More Than a Dream; March 1, 2002: "Are you secure about your security?"; November 1, 2002: "Where's the beef? Why we need quality"
- April 1, 2004: "A software odyssey-From craft to engineering"July 1, 2005: "Review this-Inspections"; October 1, 2006: "Bold predictions of quality"; May 1, 2008: "Crash dummies: Resilience"; October 1, 2008: "Nailing the nominals"; Chapter 6: Software Design If We Have Time; September 1, 2001: "A tragedy of error handling"; February 1, 2002: "Too many cooks spoil the broth-Sole authority"; May 1, 2004: "Resolved by design"; February 1, 2006: "The other side of quality-Designers and architects"; August 1, 2006: "Blessed isolation-Better design"
- November 1, 2007: "Software performance: What are you waiting for?"
