Quote:
Originally Posted by Katsunami
This way of thinking is exactly the reason why I see such a shitload of crap code that is hacked together; it works, but nobody knows why.
While you don't need a master's degree for many IT jobs, a bachelor often IS required, or you'll only attract people who taught themselves to write code. They don't have the slightest idea how to design a piece of software. They'll just start writing code and keep hacking until it, somehow, works.
|
My experience is that a programmer's education level has absolutely no relation on their ability to program, nor the quality of the resulting code.
Quote:
Originally Posted by Katsunami
I'm not selling anything. I write embedded software. If a bug is encountered, an entire factory can come to a standstill. It is imperative that someone can log into the machine, see the status of all the hardware *AND* software parts, and quickly find the part of the code that creates the problem.
Worst case, an entirely new subprocedure or component has to be written *on the spot* to get rid of some extremely nasty bugs, as a drop-in replacement for the old one. That can only be done if a piece of software is designed well. If procedures are entangled because the code was hacked together due to lack of good design, it's impossible to fix.
|
Emergency fixes of the sort you describe have nothing to do with well designed code. You find out where the broken bit is, figure out the fix, and apply it, regardless of the underlying quality of the system.
I'll grant you that the process is easier if the system is well designed...