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 our better...
| Autor principal: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Sebastopol :
Microsoft Press
2007.
|
| Edición: | 1st edition |
| Colección: | Best practices I.M. Wright's "Hard code"
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009626973006719 |
Tabla de Contenidos:
- Cover; Copyright Page; Reader Acclaim for I. M. Wright's "Hard Code" Column; Table of Contents; Foreword; Introduction; How This Book Happened; Who This Book Is For; How This Book Is Organized; System Requirements; How Microsoft Is Organized; Sample Tools and Documents; Support for This Book; Questions and Comments; Chapter 1: Project Mismanagement; June 1, 2001: "Dev schedules, flying pigs, and other fantasies"; Richter-scale estimating; Risk management; The customer wins; October 1, 2001: "Pushing the envelopes: Continued contention over dev schedules"
- Software engineering is clearly ambiguousBelieve half of what you see and none of what you hear; Motivation: It's not just pizza and beer; Sinking on a date; May 1, 2002: " Are we having fun yet? The joy of triage."; War is hell; It's nothing personal; Five golden rules of triage; The devil is in the details; It's hard to let go, isn't it?; Take care of the little things; December 1, 2004: "Marching to death"; Stabs in the dark; A litany of failure; The turning point; The road less traveled; October 1, 2005: " To tell the truth"; Suffer from delusions; Put a fork in me
- Give me a straight answerLipstick on a pig; Look at all these rumors; I want the truth; Chapter 2: Process Improvement, Sans Magic; September 2, 2002: "Six Sigma? Oh please!"; Egads! What sorcery is this?!; Calling in the cavalry; Creating order out of chaos; October 1, 2004: "Lean: More than good pastrami"; All things in moderation; Waste not, want not; Overproduction; Go deep; Transportation; Motion; Waiting; Overprocessing; Inventory; Defects; Symbiosis; April 1, 2005: "Customer dissatisfaction"; Ignorance is bliss; Too much, too late; Agile delusions; Retracing your steps
- There's more where that came fromThe right tool for the job; Duct tape and baling wire; Customer satisfaction; March 1, 2006: "The Agile bullet"; Enemy of the truth; Get the rules straightened out; Ready for something different?; Let the man speak; You complete me; A bit extreme; Are you ready for some rugby!; The more you know; Chapter 3: Inefficiency Eradicated; July 1, 2001: "Late specs: Fact of life or genetic defect?"; For every change, churn, churn, churn; Hallway meetings; Committee meetings; Spec change requests; Prevention is the best cure; June 1, 2002: "Idle hands"
- Baby did a bad bad thingTell me what I must do; Waste not, want not; June 1, 2004: "The day we met"; Why are we here?; What are we trying to do?; Why are they here?; Why am I hearing this now?; What are the next steps?; July 1, 2006: "Stop writing specs, co-located feature crews"; Have you lost your mind?; Therein lies a dilemma; Special needs; I don't recall; Stick to one thing; You ready?; February 1, 2007: "Bad specs: Who is to blame?"; It's a setup; Communication breakdown; Keep it simple and easy; Make it robust; Get feedback; Check that quality is built in; What's the difference?
- Chapter 4: Cross Disciplines
