The document discusses the characteristics of a pragmatic programmer, which include being an easy adapter, inquisitive critical thinker, realistic, and familiar with various technologies. It emphasizes communication, taking responsibility, avoiding broken windows, estimating to avoid surprises, refactoring when needed, and thorough testing. The pragmatic approach involves unambiguous representations, reversibility, programming close to the problem domain, and following the Law of Demeter.

2. What makes a Pragmatic programmer?
™ Easy adopter / fast adapter
™ Inquisitive – You tend to ask questions
™ Critical thinker – You rarely takes the things as given
™ Realistic – This gives you a good feel for how difficult
things are
™ Jack of all trades – You try to be familiar with a broad
range of techs and environments

3. It’s a continuous process
Needs small amount
of daily care

4. A Pragmatic Philosophy

5. Take responsability

6. Don’t live with broken windows

8. Remember the big picture

10. Communicate!
™ Know what you want to say
™ Know your audience
™ Choose your moment
™ Choose a style
™ Make it look good
™ Involve your audience
™ Be a listener

11. A pragmatic approach (I)
“Every piece of knowledge must have
a single, unambiguous, authoritative
representation within a system”

12. A pragmatic approach (II)
™ Make it easy to reuse
™ Reversibility: There are no final decisions!
™ Domain languages: “Program close to the problem
domain”
™ Estimate to avoid surprises

13. Law of Demeter

14. When you should refactor
™ Duplication
™ Non-Orthogonal design
™ Outdated knowledge – Things change, code needs to keep
up
™ Performance
™ PS: Avoid temporal coupling, always design for concurrency

15. Test!
™ Unit tests
™ Integration tests
™ Performance tests
™ Usability tests
™ Validation and verification