News for hackers. Stuff that matters.
Re:Programmer Competency Matrix by Jimmy on Wednesday April 08, 2015 @11:12AM (#9341246)
Why isn't there a row for "figuring out how large, poorly-documented legacy systems work"? That's what most of my daily development tasks consist of, anyway.
Re:Programmer Competency Matrix by golergka on Wednesday April 08, 2015 @12:05PM (#9341739)
Also, anger management.
Re:Programmer Competency Matrix by matthewrhoden1 on Wednesday April 08, 2015 @12:15PM (#9341831)
I couldn't agree more. Unless it's a startup, or the company produces "throw away" solutions. You're usually dropping in on a product where either the previous team was fired or it was boot-strapped by one guy who knew was he was doing, supported by 5 junior devs fresh out of college.
Re:Programmer Competency Matrix by vonmoltke on Wednesday April 08, 2015 @12:25PM (#9341893)
Don't forget the oh-so-common "We've built our core library up over years of different products, so it's kind of a mess".
Re:Programmer Competency Matrix by amelius on Wednesday April 08, 2015 @12:04PM (#9341727)
Unfortunately, most new stuff on e.g. github isn't much better in this respect. So this is a competence most programmers have.