3 ms·
A) Actually, we have plenty of ways of measuring software engineering competence.[1][2][3] B) Weirdly, all of them are heavily process focused and none of them
by mcguire 10y ago
A) Actually, we have plenty of ways of measuring software engineering competence.[1][2][3]
B) Weirdly, all of them are heavily process focused and none of them have much interest in the ability to write functioning code, because
C) Software engineering, as a field, is built on the belief that anyone can write software if properly managed.[4]
[1] http://cmmiinstitute.com/ http://cmmiinstitute.com/
[2] http://www.sei.cmu.edu/certification/ http://www.sei.cmu.edu/certification/
[3] https://www.computer.org/web/education/certifications https://www.computer.org/web/education/certifications
[4] and that would make software development much cheaper.
- mannykannot 10y agoRe C): Indeed - and the belief extends to the proposition that to properly manage it, you do not need much understanding of what the detailed design and coding aspects of development actually entail, so long as you know Software Engineering.
- mcguire 10y agoThat is an extension of the old 'managers need to know how to manage, not how to do things.'
- BatFastard 10y agoIndeed anyone can write software. However writing good, maintainable, scalable software is a totally different thing. There are so many skills (someone posted a skill matrix recently which I liked). I taught martial arts for many years, and I can honestly say that I can teach martial arts to anyone. However 98% of those learning will suck at it. They don't have the aptitude, the dedication, or pain tolerance.