Earlier quoted context omitted.
What a great quote. I wonder where it came from.
I believe the origin is in medicine. My wife introduced the idea too me 10 years ago. In medical practice, watch out for the doctor who's been practicing the same year of medicine over and over and over.
Programmer Competency Matrix
121–127 of 127 posts
Re: Programmer Competency Matrix
#122Earlier quoted context omitted.
Agreed. I'm not sure how 'Source Code Version Control' and 'Build Automation' is anywhere near the words 'Software Engineering'. And 'Automated Testing' isn't a given at a lot of shops. Professionally, I've never set up version control. It's there when I start the job, it'll be there when I leave. I've branched and merged but a lot of times this is handled by a build manager. Build automation I have never expressly d…
Let me get this straight, you do not know how to set up version control, therefore knowing how to set up version control is useless? It's not hard to start a Git repo you know, it's something you can pick up in under a day.
Re: Programmer Competency Matrix
#123Earlier quoted context omitted.
I work with PHP and javascript so I already knew I was scum...
Hey now, don't be so hard on yourself - at least you work with Javascript ;)
Re: Programmer Competency Matrix
#124Earlier quoted context omitted.
Let me get this straight, you do not know how to set up version control, therefore knowing how to set up version control is useless? It's not hard to start a Git repo you know, it's something you can pick up in under a day.
It wouldn't be useless but it could be unnecessary. I don't anticipate ever needing to set up version control, unless it's my own business. Any place I work will almost certain already have it set up, and if not, someone else will be tasked to set it up.
Re: Programmer Competency Matrix
#125Earlier quoted context omitted.
What a great quote. I wonder where it came from.
This is a quote I use very often! As with many other great quotes, I think it originates in English from Trevanian's Shibumi (when Otake-san, the Go master is giving his final teaching to Nicholai): Do not fall into the error of the artisan who boasts of twenty years experience in his craft while in fact he has had only one year of experience — twenty times. Most probably Trevanian has drawn upon some other source, t…
Re: Programmer Competency Matrix
#126Earlier quoted context omitted.
On the contrary, it is useful to have a comprehensive, substantive measure of technical skills. Having one does not preclude additional assessments, as you assume. I have been continually disappointed with the lack of extensiveness in technical interviews, as a candidate, but also as an interviewer when reviewing other interviewer assessments of potential candidates. I have yet to meet a programmer who doesn't believ…
The problem is that you're relying on interviews to hire someone who will hopefully work with you for years to come. Would you interview and pick your wife or husband in one day? Would a table like the above help?
Re: Programmer Competency Matrix
#127Earlier quoted context omitted.
Agreed. I'm not sure how 'Source Code Version Control' and 'Build Automation' is anywhere near the words 'Software Engineering'. And 'Automated Testing' isn't a given at a lot of shops. Professionally, I've never set up version control. It's there when I start the job, it'll be there when I leave. I've branched and merged but a lot of times this is handled by a build manager. Build automation I have never expressly d…
Let me get this straight, you do not know how to set up version control, therefore knowing how to set up version control is useless? It's not hard to start a Git repo you know, it's something you can pick up in under a day.
Let me get this straight, you do not know how to set up version control, therefore knowing how to set up version control is useless?
What I said:
Professionally, I've never set up version control.
I also never said it was useless. In fact, I use it at work AND at home on my own projects religiously.
However, I don't feel a need to ask about it in an interview. If you haven't used one you will be soon and if you know how to manage one it's just gravy. I might not even ask it's so inconsequential. Continuous integration is the same.
And no matter how you spin it, it's not software engineering. Not in the ballpark, not even the same game.