Hadron said:
I was referring to the MS Windows programming methodologies comment. The
"less disciplined" bit is crap too. Most projects are so damn
disciplined these days they have certificates coming out of their cracks
but very little SW. OSS is a different kettle of fish - almost zero
discipline and "yet another copycat program" every other day.
A good process as squat to do with "certificates". In fact the best people
I know in software engineering have degrees/diploma but no certifications,
they are viewed as a wasted effort in advanced levels of software
engineering. Certs are for those that are new, need to show they have a
minimum competency level. Any meaningful certifications are the ones for
the processes and the verification that they are being followed buy the lab.
I was referring to the process of good software design. Requirements,
business cases, documentation, cost analysis, risk, evolution of processes
in a full SQA model.
http://en.wikipedia.org/wiki/Software_Quality_Assurance
How many Microsoft shops have a working SQA modeled process? Many don't
even have a QA position, and if they do they are under funded and under
staffed often without written test plans. How many even have centrally
managed and monitored document/source code control? Source Safe, LOL.
Coding is often ad-hoc and not peer reviewed. Lets not get into the lack of
design documentation, absence of solid planning, requirements and risk
analysis. How many Microsoft projects are on time? Vista anyone?
If you are writing command and control code for something like a nuclear
warship, it isn't like your average I/T shop, or I hope not. Lets whip out
some .NET and some XML because it is whey cool does not float, but might get
you fired. Coding in a well designed and managed project is really just a
short mechanical exercise near the middle-end of the project cycle. On
time, on budget and delivers exactly what is required.