Programmer Competency Matrix

Re:Programmer Competency Matrix by RyanZAG on Wednesday June 19, 2013 @09:28AM (#5905388)

Usual misunderstanding, but needs to be pointed out:

  Automated testing

  Level 1:
    Has written automated unit tests and comes up with 
    good unit test cases for the code that is being written	

  Level 2:
    Has written code in TDD manner

TDD is not for testing, TDD is for system design and an automatic work list. Using TDD does not mean the automated tests are better or worse - you are probably thinking of code coverage.

[ Parent | on HN ]

Re:Programmer Competency Matrix by six on Wednesday June 19, 2013 @09:39AM (#5905434)

Not to start another flame war on (T|B)DD, but (T|B)DD does not guarantee competence in any way, and I wouldn't force it on any of the engineers who work for me.

[ Parent | on HN ]

Re:Programmer Competency Matrix by wglb on Wednesday June 19, 2013 @12:16PM (#5906417)

I thought the second 'D' in TDD was for Development, not Design. I don't think it works to write failing tests and have that influence the design.

[ Parent | on HN ]

Re:Programmer Competency Matrix by whimsy on Wednesday June 19, 2013 @09:22PM (#5909599)

What would you recommend as a substitution for that entry?

[ Parent | on HN ]