Cargando…
Understanding Software.
Software legend Max Kanat-Alexander shows you how to succeed as a developer by embracing simplicity, with forty-three essays that will help you really understand the software you work with. About This Book Read and enjoy the superlative writing and insights of the legendary Max Kanat-Alexander Learn...
| Clasificación: | Libro Electrónico |
|---|---|
| Autor principal: | |
| Formato: | Electrónico eBook |
| Idioma: | Inglés |
| Publicado: |
Packt Publishing,
2017.
|
| Temas: | |
| Acceso en línea: | Texto completo |
Tabla de Contenidos:
- Cover
- Copyright
- Credits
- About the Author
- www.PacktPub.com
- Customer Feedback
- Table of Contents
- Foreword
- Part One: Principles for Programmers
- Chapter 1: Before You Beginâ#x80;Œ
- 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
- Starting the Right Way
- Chapter 10: The Accuracy of Future Predictions
- Chapter 11: Simplicity and Strictness
- Chapter 12: Two is Too Many
- Refactoring
- 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
- Compounding ComplexityChapter 16: Make It Never Come Back
- Make it Never Come Back â#x80;#x93; An Example
- Down the Rabbit Hole
- Chapter 17: The Fundamental Philosophy of Debugging
- Clarify the Bug
- Look at the System
- Find the Real Cause
- Four Steps
- Part Five: Engineering in Teams
- Chapter 18: Effective Engineering Productivity
- The Solution
- Chapter 19: Measuring Developer Productivity
- Chapter 20: How to Handle Code Complexity in a Software Company
- Step 1 â#x80;#x93; Problem Lists
- Step 2 â#x80;#x93; Meeting
- Step 3 â#x80;#x93; Bug Reports
- Step 4 â#x80;#x93; PrioritizationStep 5 â#x80;#x93; Assignment
- Step 6 â#x80;#x93; Planning
- Chapter 21: Refactoring is about Features
- Being Effective
- Refactoring Doesn't Waste Time, It Saves It
- Refactoring To Clarity
- Summary
- Chapter 22: Kindness and Code
- Software is about People
- Chapter 23: Open Source Community, Simplified
- Retaining Contributors
- Removing the Barriers
- Getting People Interested
- Summary
- Part Six: Understanding Software
- Chapter 24: What is a Computer?
- Chapter 25: The Components of Software: Structure, Action, and ResultsChapter 26: Software Revisited: (I)SAR Clarified
- Structure
- Action
- Results
- ISAR in a Single Line of Code
- Wrapping SAR Up
- Chapter 27: Software as Knowledge
- Chapter 28: The Purpose of Technology
- Are there Counter-Examples to this Rule?
- Is the Advance of Technology Good?
- Chapter 29: Privacy, Simplified
- Privacy of Space
- Privacy of Information
- A Summary of Privacy
- Chapter 30: Simplicity and Security