Understanding Software chapters
About this audiobook · Recording details
Recording steve-menasche-2019 · Narrated by Steve Menasche
Showing 100 of 157 chapters
| Chapter | Title | Start | Duration |
|---|---|---|---|
| 1 | Opening Credits | 0:00:00 | 0:00:28.567 |
| 2 | Foreword | 0:00:28.567 | 0:06:08.215 |
| 3 | Part One: Principles for Programmers | 0:06:36.782 | 0:00:06.879 |
| 4 | 1. Before You Begin… | 0:06:43.661 | 0:03:06.903 |
| 5 | If You're Going To Do It Then Do it Well | 0:09:50.564 | 0:01:16.637 |
| 6 | 2. The Engineer Attitude | 0:11:07.201 | 0:04:02.996 |
| 7 | 3. The Singular Secret of the Rockstar Programmer | 0:15:10.197 | 0:04:23.848 |
| 8 | 4. Software Design, in Two Sentences | 0:19:34.045 | 0:00:44.884 |
| 9 | Part Two: Software Complexity and its Causes | 0:20:18.929 | 0:00:07.370 |
| 10 | 5. Clues to Complexity | 0:20:26.299 | 0:01:18.706 |
| 11 | 6. Ways To Create Complexity: Break Your API | 0:21:45.005 | 0:06:35.993 |
| 12 | 7. When Is Backwards-Compatibility Not Worth It? | 0:28:20.998 | 0:04:56.565 |
| 13 | 8. Complexity is a Prison | 0:33:17.563 | 0:03:47.741 |
| 14 | Part Three: Simplicity and Software Design | 0:37:05.304 | 0:00:07.584 |
| 15 | 9. Design from the Start | 0:37:12.888 | 0:01:33.278 |
| 16 | Starting the Right Way | 0:38:46.166 | 0:01:34.905 |
| 17 | 10. The Accuracy of Future Predictions | 0:40:21.071 | 0:06:12.076 |
| 18 | 11. Simplicity and Strictness | 0:46:33.147 | 0:07:10.892 |
| 19 | 12. Two is Too Many | 0:53:44.039 | 0:03:30.709 |
| 20 | Refactoring | 0:57:14.748 | 0:02:21.421 |
| 21 | 13. Sane Software Design | 0:59:36.169 | 0:01:06.942 |
| 22 | The Wrong Way | 1:00:43.111 | 0:02:29.741 |
| 23 | Analysis of The Wrong Way | 1:03:12.852 | 0:01:25.408 |
| 24 | Bringing It To a Group | 1:04:38.260 | 0:02:28.135 |
| 25 | The Right Way | 1:07:06.395 | 0:02:27.935 |
| 26 | We followed all the Laws Of Software Design | 1:09:34.330 | 0:01:36.301 |
| 27 | Part Four: Debugging | 1:11:10.631 | 0:00:05.532 |
| 28 | 14. What is a Bug? | 1:11:16.163 | 0:02:12.962 |
| 29 | Hardware | 1:13:29.125 | 0:00:38.651 |
| 30 | 15. The Source of Bugs | 1:14:07.776 | 0:02:23.032 |
| 31 | Compounding Complexity | 1:16:30.808 | 0:02:51.714 |
| 32 | 16. Make It Never Come Back | 1:19:22.522 | 0:02:58.936 |
| 33 | Make it Never Come Back – An Example | 1:22:21.458 | 0:06:07.713 |
| 34 | Down the Rabbit Hole | 1:28:29.171 | 0:01:23.772 |
| 35 | 17. The Fundamental Philosophy of Debugging | 1:29:52.943 | 0:03:35.894 |
| 36 | Clarify the Bug | 1:33:28.837 | 0:02:44.650 |
| 37 | Look at the System | 1:36:13.487 | 0:02:19.602 |
| 38 | Find the Real Cause | 1:38:33.089 | 0:02:11.558 |
| 39 | Four Steps | 1:40:44.647 | 0:02:23.347 |
| 40 | Part Five: Engineering in Teams | 1:43:07.994 | 0:00:06.578 |
| 41 | 18. Effective Engineering Productivity | 1:43:14.572 | 0:03:27.163 |
| 42 | So What Should You Do? | 1:46:41.735 | 0:03:00.261 |
| 43 | The Solution | 1:49:41.996 | 0:04:06.927 |
| 44 | Credibility and Solving Problems | 1:53:48.923 | 0:02:56.235 |
| 45 | The Blocker | 1:56:45.158 | 0:04:10.461 |
| 46 | Moving Towards the Fundamental Problem | 2:00:55.619 | 0:04:51.137 |
| 47 | 19. Measuring Developer Productivity | 2:05:46.756 | 0:01:43.635 |
| 48 | The Definition of "Productivity" | 2:07:30.391 | 0:00:55.638 |
| 49 | Why Not "Lines of Code?" | 2:08:26.029 | 0:02:59.928 |
| 50 | Determining a Valid Metric | 2:11:25.957 | 0:02:47.153 |
| 51 | What About When Your Product Is Code? | 2:14:13.110 | 0:01:06.144 |
| 52 | What about People Who Work on Developer Productivity? | 2:15:19.254 | 0:03:28.464 |
| 53 | Conclusion | 2:18:47.718 | 0:00:45.180 |
| 54 | 20. How to Handle Code Complexity in a Software Company | 2:19:32.898 | 0:03:10.004 |
| 55 | Step 1 – Problem Lists | 2:22:42.902 | 0:01:19.889 |
| 56 | Step 2 – Meeting | 2:24:02.791 | 0:01:50.002 |
| 57 | Step 3 – Bug Reports | 2:25:52.793 | 0:00:34.270 |
| 58 | Step 4 – Prioritization | 2:26:27.063 | 0:03:00.903 |
| 59 | Step 5 – Assignment | 2:29:27.966 | 0:01:06.069 |
| 60 | Step 6 – Planning | 2:30:34.035 | 0:01:56.359 |
| 61 | 21. Refactoring is about Features | 2:32:30.394 | 0:02:03.419 |
| 62 | Being Effective | 2:34:33.813 | 0:06:03.309 |
| 63 | Setting Refactoring Boundaries | 2:40:37.122 | 0:01:05.369 |
| 64 | Refactoring Doesn't Waste Time, It Saves It | 2:41:42.491 | 0:01:25.215 |
| 65 | Refactoring To Clarity | 2:43:07.706 | 0:02:26.986 |
| 66 | Summary | 2:45:34.692 | 0:01:13.981 |
| 67 | 22. Kindness and Code | 2:46:48.673 | 0:01:05.323 |
| 68 | Software is about People | 2:47:53.996 | 0:01:48.137 |
| 69 | An Example of Kindness | 2:49:42.133 | 0:02:52.727 |
| 70 | Be Kind, and Make Better Software | 2:52:34.860 | 0:01:16.996 |
| 71 | 23. Open Source Community, Simplified | 2:53:51.856 | 0:01:27.044 |
| 72 | Retaining Contributors | 2:55:18.900 | 0:01:21.800 |
| 73 | 1. Don't Freeze the Trunk for Long Periods | 2:56:40.700 | 0:02:31.017 |
| 74 | 2. Turnover Is Inevitable | 2:59:11.717 | 0:01:08.481 |
| 75 | 3. Respond to Contributions Immediately | 3:00:20.198 | 0:01:28.512 |
| 76 | 4. Be Extremely Kind and Visibly Appreciative | 3:01:48.710 | 0:02:55.452 |
| 77 | 5. Avoid Personal Negativity | 3:04:44.162 | 0:03:24.815 |
| 78 | Removing the Barriers | 3:08:08.977 | 0:00:45.096 |
| 79 | 1. A List of Easy Starting Projects | 3:08:54.073 | 0:00:27.371 |
| 80 | 2. Create and Document Communication Channels | 3:09:21.444 | 0:02:09.203 |
| 81 | 3. Excellent, Complete, and Simple Documentation, Describing Exactly how A Contribution Should Be Done | 3:11:30.647 | 0:01:05.440 |
| 82 | 4. Make All This Documentation Easy to Find | 3:12:36.087 | 0:01:14.250 |
| 83 | Getting People Interested | 3:13:50.337 | 0:01:07.852 |
| 84 | Be a Super-Popular Product | 3:14:58.189 | 0:01:00.092 |
| 85 | Be Written in A Popular Programming Language | 3:15:58.281 | 0:01:30.400 |
| 86 | Summary | 3:17:28.681 | 0:00:34.538 |
| 87 | Part Six: Understanding Software | 3:18:03.219 | 0:00:06.955 |
| 88 | 24. What is a Computer? | 3:18:10.174 | 0:04:29.571 |
| 89 | 25. The Components of Software: Structure, Action, and Results | 3:22:39.745 | 0:03:17.926 |
| 90 | 26. Software Revisited: (I)SAR Clarified | 3:25:57.671 | 0:01:40.459 |
| 91 | Structure | 3:27:38.130 | 0:02:05.852 |
| 92 | Action | 3:29:43.982 | 0:00:59.804 |
| 93 | Results | 3:30:43.786 | 0:01:28.943 |
| 94 | ISAR in a Single Line of Code | 3:32:12.729 | 0:01:14.234 |
| 95 | Wrapping SAR Up | 3:33:26.963 | 0:00:30.734 |
| 96 | 27. Software as Knowledge | 3:33:57.697 | 0:06:18.299 |
| 97 | 28. The Purpose of Technology | 3:40:15.996 | 0:01:36.040 |
| 98 | Are there Counter-Examples to this Rule? | 3:41:52.036 | 0:01:23.978 |
| 99 | Is the Advance of Technology "Good"? | 3:43:16.014 | 0:01:22.390 |
| 100 | 29. Privacy, Simplified | 3:44:38.404 | 0:01:17.979 |