- Software quality is more the result of a system designed to produce quality, and not so much the result of individual performance.
- Technical and human factors are involved in systemic quality, and these factors intersect and interact.
- Great tests catch errors before they become problems, but those tests don’t magically exist; they require a structure that affords the time and space to write tests.
- Outages are treated as systemic because most of them are. That’s because testing practices are so good that individual errors are caught long before they become impactful failures.
- Instead of spending tons of time and effort on hiring because you believe that you can “only hire the best”, direct some of that effort towards building a system that produces great results from a wider spectrum of individual performance.
Assorted reflections as a 40-year-old programmer
- Working with people you can learn from is a wonderful source of motivation
- Communicating effectively is a complex skill that takes years to develop and an essential one if you want to program professionally
- “No matter how it looks at first, it’s always a people problem”, by Gerald Weinberg, is essentially true and something to have very present by technically-minded people.
First make the change easy, then make the easy change
- It’s a quote from Kent Beck
- Refactoring code can be a challenge. Software projects tend to grow with time. If left unchecked, they can become unruly and hard to reason about. Spaghetti code is a term that’s never too far from such a mess.
- In a way, this quote is saying, “first do what you should have always been doing; being organized”, and “then do what you came here to do in the first place (add a feature, fix a bug).”
Jony Ive on what he misses most about Steve Jobs
- In larger groups, our conversations gravitate towards the tangible, the measurable. It is more comfortable, far easier and more socially acceptable to talk about what is known. Being curious and exploring tentative ideas were far more important to Steve than being socially acceptable.
- For Steve, wanting to learn was far more important than wanting to be right.
- Steve was preoccupied with the nature and quality of his own thinking. He expected so much of himself and worked hard to think with a rare vitality, elegance and discipline. His rigour and tenacity set a dizzyingly high bar. When he could not think satisfactorily, he would complain like I did about my knees.
- Steve truly believed that by making something useful, empowering and beautiful, we express our love for humanity.
Essential elements of a great developer experience
- Concise getting started guides
- SDKs or code libraries in popular languages
- Self-serve product sign-up
- Easy-to-find documentation
- Product change log & API status
- Sample apps & code
- Interactive docs & cURL commands
- Developer experience & community engagement