2 ms·
"Besides, saying it isn't true for good programmers is a like the No True Scotsman fallacy." No, because I can point to the people I'm referring to. In 1960, w
by jerf 17y ago
"Besides, saying it isn't true for good programmers is a like the No True Scotsman fallacy."
No, because I can point to the people I'm referring to. In 1960, we did not have a lot of dedicated QA staff, dedicated sysadmins and IT, dedicated server farms, and so on and so on. Programmers have grown up auxiliary support personnel around them. The same has been true of doctors for a long time ("nurses") and will be more true, but the core doctors will actually be dealing with less and less of the routine.
The problem with your "software is getting crappier like furniture" theses is that it's flat-out wrong. If software was today as crappy as it was in 1980, the Internet would not work. We can't have the same bug-count-per-feature we had back then, we've got a crapload more features for bugs to be in! What is true is that we've got frameworks and libraries of a quality the programmers of the 1980s could only dream of, and a programmer can take these and trade technical quality for speed of development, and while the result can still be quite messy it is simply an option that didn't exist in 1980. On the whole though, software is radically better now than it was then; the alternative is not even technically feasible, it wouldn't even begin to work.
Seriously, if you think I'm on crack, go back and find the oldest source code you can. What you remember as a shining example of bug-free code will be revealed to be code that by modern standards is barely holding together and fails to exhibit bugs only because the task it takes on is so small there's hardly any room to trick it into doing something wrong. Not a viable path going forward.