News for hackers. Stuff that matters.
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.

Re:The Best Programming Advice I Ever Got (2012) by tormeh on Sunday December 16, 2018 @07:34AM (#18692824)
One-of-a-kind construction projects are notorious for cost overruns. It's ridiculous, just like enterprise software projects.
Re:The Best Programming Advice I Ever Got (2012) by redisman on Monday December 17, 2018 @08:35PM (#18703876)
Same with civil engineering. They're building a new mass transit and it's 5 years late. Oh well.