Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent SoftwareTheir story takes us through a maze of dead ends and exhilarating breakthroughs as they and their colleagues wrestle not only with the abstraction of code but with the unpredictability of human behavior, especially their own. Along the way, we encounter black holes, turtles, snakes, dragons, axe-sharpening, and yak-shaving—and take a guided tour through the theories and methods, both brilliant and misguided, that litter the history of software development, from the famous “mythical man-month” to Extreme Programming. Not just for technophiles but for anyone captivated by the drama of invention, Dreaming in Code offers a window into both the information age and the workings of the human mind. |
Contents
CHAPTER 2 | |
CHAPTER 3 | |
2001NOVEMBER 2002 | |
CHAPTER 5 | |
CHAPTER 6 | |
CHAPTER 7 | |
CHAPTER 8 | |
CHAPTER 9 | |
CHAPTER 10 | |
CHAPTER 11 | |
EPILOGUE | |
ACKNOWLEDGMENTS | |
Other editions - View all
Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One ... Scott Rosenberg No preview available - 2008 |
Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One ... Scott Rosenberg No preview available - 2008 |
Common terms and phrases
actually already Anderson approach asked become began begin better blog bugs build built calendar called Chandler collection complex conference create detail developers document early engineering event field going hand hard Hertzfeld human ideas interface it’s Kapor keep kind language later less look machine manager means meeting Microsoft months moved never notes object offered once open source organization original OSAF OSAF’s posting problem Python questions release repository says schedule seemed sharing simply software development start started structure talk task term things trying turn users week Windows write wrote