Books+ Search Results
Understanding software : Max Kanat-Alexander on simplicity, coding, and how to suck less as a programmer
Title
Understanding software : Max Kanat-Alexander on simplicity, coding, and how to suck less as a programmer / Max Kanat-Alexander.
ISBN
9781788628341
1788628349
9781788628815
Publication
Birmingham, UK : Packt Publishing, 2017.
Physical Description
1 online resource (x, 261 pages) : illustrations
Local Notes
Access is available to the Yale community.
Notes
"Expert insight."
Includes index.
Access and use
Access restricted by licensing agreement.
Summary
In Understanding Software, Max Kanat-Alexander, Technical Lead for Code Health at Google, shows you how to bring simplicity back to computer programming. Max explains to you why programmers suck, and how to suck less as a programmer. There's just too much complex stuff in the world. Complex stuff can't be used, and it breaks too easily. Complexity is stupid. Simplicity is smart.
Variant and related titles
Max Kanat-Alexander on simplicity, coding, and how to suck less as a programmer
O'Reilly Safari. OCLC KB.
Format
Books / Online
Language
English
Added to Catalog
June 29, 2022
Contents
Part One: Principles for Programmers; Chapter 1: Before You Begin; If You're Going To Do It Then Do it Well; Chapter 2: The Engineer Attitude; Chapter 3: The Singular Secret of the Rockstar Programmer; Chapter 4: Software Design, in Two Sentences; Part Two: Software Complexity and its Causes; Chapter 5: Clues to Complexity; Chapter 6: Ways To Create Complexity: Break Your API; Chapter 7: When Is Backwards-Compatibility Not Worth It?; Chapter 8: Complexity is a Prison; Part Three: Simplicity and Software Design; Chapter 9: Design from the Start; Chapter 10: The Accuracy of Future Predictions; Chapter 11: Simplicity and Strictness; Chapter 12: Two is Too Many; Refactorin"; Chapter 13: Sane Software Design; The Wrong Way; The Right Way; We followed all the Laws Of Software Design; Part Four: Debugging; Chapter 14: What is a Bug?; Hardware; Chapter 15: The Source of Bugs; Chapter 16: Make It Never Come Back; Chapter 17: The Fundamental Philosophy of Debugging; Chapter 18: Effective Engineering Productivity; Chapter 19: Measuring Developer Productivity; Chapter 20: How to Handle Code Complexity in a Software Company; Chapter 21: Refactoring is about Features; Chapter 22: Kindness and Code; Chapter 23: Open Source Community, Simplified; Part Six: Understanding Software; Chapter 24: What is a Computer?; Chapter 25: The Components of Software: Structure, Action, and Results; Chapter 26: Software Revisited: (I)SAR Clarified; Chapter 27: Software as Knowledge
Chapter 28: The Purpose of Technology; Chapter 29: Privacy, Simplified; Chapter 30: Simplicity and Security; Chapter 31: Test-Driven Development and the Cycle of Observation; Chapter 32: The Philosophy of Testing; Chapter 33: The Secret of Success: Suck Less; Chapter 34: How We Figured Out What Sucked; Chapter 35: The Power of No; Chapter 36: Why Programmers Suck; Chapter 37: The Secret of Fast Programming: Stop Thinking; Chapter 38: Developer Hubris; Chapter 39: "Consistency" Does Not Mean "Uniformity" ^^
Chapter 40: Users Have Problems: Developers Have Solutions; Chapter 41: Instant Gratification = Instant Failure; Chapter 42: Success Comes From Execution, Not Innovation; Chapter 43: Excellent Software; Index.
Bookmark As
Citation
