Thursday, January 16, 2014

Being Pragmatic


  1. Care about your craft
  2. Think! About your work
  3. Provide options, no excuses
  4. Don't live with broken windows
  5. Be a catalyst for change
  6. Remember the big picture
  7. Make quality a requirements issue
  8. Invest regularly in your knowledge
  9. Critically analyze what you read and hear
  10. It's both what you say and how you say it


  • Know what you want to say
  • Know your audience
  • Choose your moment
  • Choose a style
  • Make it look good
  • Involve the audience
  • Be a listener
  • Respond
  1. DRY - Don't Repeat Yourself
  2. Make it easy to reuse
  3. Eliminate effects between unrelated objects
  4. There are no final decisions
  5. Use tracer bullets to find the target
  6. Prototype to learn
  7. Program close to the problem domain
  8. Estimate to avoid surprises
  9. Iterate the schedule with the code
  1. Keep knowledge in plain text
  2. Use command shells
  3. Use a single editor well
  4. Always use source control management software
  5. Fix the problem not the blame
  6. Don't panic
  7. Take the signs for what they are
  8. Don't assume it - Prove it
  9. Learn a text manipulation language
  • Debugging steps
  1. Are you seeing a symptom, or the root cause?
  2. Write down the problem as in an email to a co-worker
  3. If we see problems and the tests are passing, then are the tests complete?
  4. Where else does this problem exist, or need to be checked?

No comments:

Post a Comment