Pragmatic programmer way

[morarasu-alexandru]

-Broken Window; Stone Soup and Boiled Frogs; Good-Enough Software

• Communicate!
  -DRY Extended subject depending on audience
  -> DRY Categories: Imposed duplication, inadvertent duplication, impatient duplication, Interdeveloper duplication
  -> Documentation and code
  -Orthogonality (taken into account dry)

-Reversability + Flexible Arhitecture
-Estimate
-Design by Contract
-Assertive Programming(“If it can’t happen, use assertions to ensure that it won’t”)
-Programming by Coincidence
-Refactoring
-Ruthless testing
-Pragmatic teams

[morarasu-alexandru]

Basically the presentation is based on the following book:

The Pragmatic Programmer: From Journeyman to Master
by Andrew Hunt