Ken Pugh (computer programmer)
From EverybodyWiki Bios & Wiki
Ken Pugh is a Fellow Consultant for Net Objectives. He is active in promoting lean-agile practices and quality code.
Education
Pugh received his B.S. in electrical engineering, summa cum laude, from Duke University and his M.S.E.E. from the University of Maryland.
Contributions
Pugh's primary contributions have been in the areas of Acceptance Test-Driven Development [1] and Prefactoring[2] – guidelines for writing quality code. His book on Prefactoring won the Jolt Award in 2006[3]. He has presented at numerous US and international conferences. His current interests are lean-agile development.[4]
Selected publications
- Pugh, Ken (2011). Lean-Agile Acceptance Test-Driven Development: Better Software Through Collaboration. Addison-Wesley. ISBN 978-0321714084. Search this book on
- Pugh, Ken (2011). Prefactoring: Extreme Abstraction, Extreme Separation, Extreme Readability. O'Reilly Media. ISBN 978-0596008741. Search this book on
- Pugh, Ken (2006). Interface Oriented Design. Pragmatic Programmers. ISBN 978-0976694052. Search this book on According to WorldCat, the book is held in 129 libraries [5]
- Pugh, Ken (1990). All on C. Scott Foresman & Co. ISBN 9780673186034. Search this book on
- Pugh, Ken (1985). C Language for Programmers. Scott Foresman Trade. ISBN 9780673180346. Search this book on
- Pugh, Ken (1994). Unix For MS-DOS Users. Prentice Hall Ptr. ISBN 9780131460775. Search this book on
References
- ↑ Pugh, Ken (2011). Lean-Agile Acceptance Test-Driven Development: Better Software Through Collaboration. Addison-Wesley. ISBN 978-0321714084. Search this book on
- ↑ Pugh, Ken (2011). Prefactoring: Extreme Abstraction, Extreme Separation, Extreme Readability. O'Reilly Media. ISBN 978-0596008741. Search this book on
- ↑ "Jolt Award 2006". Retrieved 2014-01-23.
- ↑ Pugh, Ken; Shalloway, Alan; Bain, Scott; Kolsky, Amir (2011). Essential Skills for the Agile Developer. Addison-Wesley Professional. ISBN 978-0321543738. Search this book on
- ↑ WorldCat item record
Further reading
- Downs, Gary (July 2011). "Lean-agile acceptance test-driven development: better software through collaboration by Ken Pugh". ACM SIGSOFT Software Engineering Notes. 36 (4): 34. doi:10.1145/1988997.1989006.
- Kalfatovic, Martin R. (June 2007). "REVIEW OF Ken Pugh. (2006). Interface-Oriented Design. Raleigh, NC: The Pragmatic Programmer (ISBN 0976694050). 215 pp. 29.95". Technology Electronic Reviews. 14 (1).
- Mateosian, Richard (2006). "So Many Books". IEEE Micro. 26 (5): 82–83. doi:10.1109/MM.2006.99.
Selected Reviews
- "Interface Oriented Design Review". Retrieved 2015-06-25.
- "Prefactoring Review". Retrieved 2015-06-25.
- "Acceptance Test-Driven Development Seminar Review by Steven Boles". Retrieved 2015-06-25.
- "Acceptance Test-Driven Development Review". Retrieved 2015-06-25.
- "Prefactoring Review". Retrieved 2015-06-25.
Selected Conference Talks
- "Determining Business Value" (PDF). Retrieved 2015-06-25.
- "Acceptance Test-Driven Development Seminar" (PDF). Retrieved 2015-06-25.
Selected Citations
- "Syllabi Using Interface-Oriented Design". Retrieved 2015-06-25.
- "Acceptance Test-Driven Development" (PDF). Retrieved 2015-06-25.
- "Test-Driven Infrastructure with Chef: Bring Behavior-Driven Development to Infrastructure as Code". Retrieved 2015-06-25.
Selected Interviews
- "Acceptance Test-Driven Development Interview by Bob Payne". Retrieved 2015-06-25.
- "How to Improve Communication Between QA and Development". Retrieved 2015-06-25.
- "Creative Software Testing in Agile Environments". Retrieved 2015-06-25.
- "Acceptance Test-Driven Development Interview by Matthew Heusser". Retrieved 2015-06-25.
External links
- "Introductory Acceptance Test". Retrieved 2014-01-23.
- "Prefactoring". Retrieved 2014-01-23.
- Pugh, Ken "The Risks of Acceptance Test Debt (Cutter Consortium)". Retrieved 2014-01-23.
- Pugh, Ken "What is Acceptance Test-Driven Development". Retrieved 2014-01-23.
- Net Objectives
- Pugh-Killeen Associates
This article "Ken Pugh (computer programmer)" is from Wikipedia. The list of its authors can be seen in its historical. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.
