Re:The Best Programming Advice I Ever Got (2012)
by eikenberry on Saturday December 15, 2018 @06:14PM
(#18690877)
Individual "masters craftsmen" have always figured out things like this way before they have become common practice. But I think original poster was meaning "we" as a profession stabilizing on standard good practices that everyone knows and uses, not just a few masters.
Re:The Best Programming Advice I Ever Got (2012)
by ken on Saturday December 15, 2018 @08:33PM
(#18691290)
> A lot of people figured it out already..
You'll have to expand on this for me, because I find this claim shocking. Who figured it out, and what did they figure out?
Re:The Best Programming Advice I Ever Got (2012)
by leaveyou on Sunday December 16, 2018 @04:40AM
(#18692421)
Software is not the first industry to deal with systems complexity or large teams management but (in my part of the world at least) it's the first to expect engineering-like results from non-engineering workers and managers. There are developers who have noticed the similarities between creating/assembling/testing components & modules in other industries and software and borrowed practices before software had a name for them. It's just that these people are dispersed in a sea of devs tuned to Microsoft Framework Factory or busy building castles on Javascript Frameworks Sands.
Re:The Best Programming Advice I Ever Got (2012)
by tormeh on Sunday December 16, 2018 @05:13AM
(#18692479)
What other industries should we learn from?
I know big construction projects often suffer from similar problems, and they don't seem to have figured it out.
Re:The Best Programming Advice I Ever Got (2012)
by leaveyou on Sunday December 16, 2018 @05:26AM
(#18692512)
Auto.
I find it quite strange that you are not aware about how much more reliable & secure is the product of the construction industry compared to software.
I don't think anyone argues with that. It's just that sometimes some of the biggest impostors hide behind "boundaries".
>>This will continue to be a problem for the next 100 years until we figure out the right way to make good software.
A lot of people figured it out already.. but those are a minority and the field is fueled continually with poorly instructed people. The Business can't distinguish quickly between these two categories and often it does not even bother (good interviewing is hard or expensive) because (in Europe) it's not the software efficiency or other quality making the profit.