--Originally published at TI2011 – Project Evaluation and Management
Final review for The Pragmatic Programmer by Hunt, A. & Thomas, D.
The book contains a quick reference guide with 70 tips using entertaining anecdores to explain the way the autors made his workflow more efficient and very productive.
So here is the review of all the 70 tips:
- Care about your craft – Why you soend your life developing software?
- Think! About your work – Take control, explain what can be done.
- Provide options, Don’t make LAME excuses
- Don’t live with broken windows – Fix bad designs, wrong decisions and poor code
- Be a Catalyst for Change – Show how can it be and help in creating it.
- Remember the Big Picture – Check what’s happening around you.
- Make quality a requirements issue – involve users to determinate the real quality
- Invest regularly in your knowledge portafolio – make learning a habit
- Critically Analyze What you read and hear – analyze information in terms of you and your project
- It’s both what you say and the way you say it – Know how to communicate effectively your ideas
- DRY – DON’T REPEAT YOURSELF – Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.
- Make it easy to reuse – it it’s easy to reuse, people will.
- Eliminate effects between unrelated things – Design components that are indepentedent and self-contained
- There are no final decisions – No decision is cast in STONE
- Use tracer bullets to find the target
- Prototype to Learn – Prototyping is a learning experience
- Program Close to the Problem Domain – Design and code in your user’s language.
- Estimate to avoid surprises – Estimate before you start.
- Iterate the schedule with the code – Use experience you gain as you implement to refine the project.
- Keep Knowledge in Plain Text – It helps start your Continue reading "I’m a Pragmatic Programmer"