skip to main | skip to sidebar

Software Quality Assurance

An approach to Software Quality Assurance based on experience and education. From the fundamentals and corner stones to the the complexities and obscure.

Wednesday, November 5, 2008

Navajo Tradition of development

When there is no documentation either via comments or business requirement documentation or flow chart, when all you have are the words of your predecessor and maybe some instruction on how they performed the functions of their job.
Posted by Jeremiah at 10:06 PM

No comments:

Post a Comment

Newer Post Older Post Home
Subscribe to: Post Comments (Atom)

Blog Archive

  • ►  2022 (8)
    • ►  March (2)
    • ►  February (4)
    • ►  January (2)
  • ►  2021 (10)
    • ►  December (5)
    • ►  November (2)
    • ►  October (1)
    • ►  September (1)
    • ►  August (1)
  • ►  2018 (2)
    • ►  September (1)
    • ►  August (1)
  • ►  2016 (5)
    • ►  July (5)
  • ►  2012 (1)
    • ►  February (1)
  • ►  2010 (1)
    • ►  May (1)
  • ►  2009 (9)
    • ►  July (1)
    • ►  June (2)
    • ►  April (1)
    • ►  February (2)
    • ►  January (3)
  • ▼  2008 (10)
    • ►  December (1)
    • ▼  November (5)
      • Regression Testing
      • When code breaks, keep breaking it...
      • Most Software Stinks! and beyond
      • Navajo Tradition of development
      • Unit testing: When dev smokes in the sandbox QA cl...
    • ►  October (2)
    • ►  June (2)

About Me

My photo
Jeremiah
View my complete profile