This is someone's (very arbitrary) opinion in a grid. I hope you don't actually interview people. Figuring out someone's skill level is a soft science; it takes months after a hire to really know where someone is. Some people I know are great at fixing bugs but have narrow language experience. They're damn valuable. Others integrate well into teams and provide great product feedback. Where's that on here? Experience…
Some people have 10 years of experience. Others have 1 year of experience 10 times.
Programmer Competency Matrix
61–70 of 127 posts
Re: Programmer Competency Matrix
#62Re: Programmer Competency Matrix
#63Sounds pretty accurate. :)
Re: Programmer Competency Matrix
#64According to this, I'm a worthless newb. Sounds pretty accurate. :)
Re: Programmer Competency Matrix
#65Earlier quoted context omitted.
Some people have 10 years of experience. Others have 1 year of experience 10 times.
What a great quote. I wonder where it came from.
Re: Programmer Competency Matrix
#66Earlier quoted context omitted.
Some people have 10 years of experience. Others have 1 year of experience 10 times.
What a great quote. I wonder where it came from.
Re: Programmer Competency Matrix
#67Re: Programmer Competency Matrix
#68I'm not sure this has anything to do with "competency". When I was in high school, I implemented a kd-tree for a ray tracer using photon mapping. I knew that my n^2 algorithm was slow and that there was probably a better way, so I Googled and figured out how to write code for such a structure. Since I'm not a programmer (I'm a chemical engineer), I don't instantly know all of the orders of various algorithms (which a…
Re: Programmer Competency Matrix
#69Inexperienced programmers consult documentation a lot and the more experienced you become, the less you consult documentation? If this were true, the initialism "RTFM" would never have been coined.