Why bad scientific code beats code following “best practices” (2014)

Re:Why bad scientific code beats code following “best practi... by coliveira on Sunday August 28, 2016 @07:20PM (#12379017)

> Could it be that best practices are designed to make sure mediocre programmers working together produce decent code?

Yes, it is, but the issue is that the industry should move away from the idea that software can be done in an assembly line. It is better to have a few highly qualified people capable of writing complex software than a thousand mediocre programers that use GoF patterns everywhere.

[ Parent | on HN ]

Re:Why bad scientific code beats code following “best practi... by saint_fiasco on Sunday August 28, 2016 @08:02PM (#12379170)

Why? The assembly line doesn't need elite hackers, and there aren't that many elite hackers around. There is a place for cost-effective development.

[ Parent | on HN ]

Re:Why bad scientific code beats code following “best practi... by phaus on Monday August 29, 2016 @01:58AM (#12380275)

I'm a security analyst, not a developer so please forgive my ignorance, but how do you become one of the highly qualified coders without first spending some time being a mediocre developer?

[ Parent | on HN ]

Re:Why bad scientific code beats code following “best practi... by quotemstr on Monday August 29, 2016 @02:13AM (#12380324)

You don't. There's no way around having to spend some time in the trenches --- but we can at least minimize the amount of time developers spend in the sophomoric architecture-astronaut intermediate phase by not glorifying excess complexity. Ultimately, though, there's not a good way to teach good taste except to provide good examples.

[ Parent | on HN ]