The Pragmatic Programmer - Chapter 1: A Pragmatic Philosophy
The Pragmatic Programmer - Chapter 1: A Pragmatic Philosophy
1. It’s Your Life: You have agency. Do it!!!
- Think beyond the problem.
- Consider the bigger picture.
- Take responsibility of the code.
2. The Cat Ate My Source Code
- The greatest of all weakness is the fear of appearing weak.
- Things go wrong.
- Trust your team.
- Take responsibility.
- Don’t blame someone or something else. Don’t make up an excuse.
- Prove options.
- “I don’t know, but I’ll find out!”
3. Software Entropy
- When disorder increases in software we call it “Technical Dept”.
- Hopelesness can be contagious.
- Don’t live with broken windows.
- Don’t let entropy win.
4. Stone Soup and Boiled Frogs
- Be a catalyst for change.
- It’s easier to ask forgiveness than it is to get permission.
- Remember the big picture.
5. Good Enough Software
- Make quality a requirement issue.
6. Your Knowledge Portfolio
- An investment in knowledge always pays the best interest.
- Don’t put all your technicall eggs in one basket.
- Invest regularly in your knowledge portfolio.
7. Communicate
- A good idea is an orphan without effective communication.
- Know your audience.
- Know what you want to say.
- Choose your moment.
- Choose a style.
- Make it look good.
- Be a listener.
- Get back to people.
- The more effective your communication, the more influential you become.
- Build documentation in, don’t bolt it on.
- “Bolt something on”: add something in a rush way, treating as secondary need.
This post is licensed under CC BY 4.0 by the author.