News for hackers. Stuff that matters.
Re:Why bad scientific code beats code following “best practi... by pkroll on Sunday August 28, 2016 @02:23PM (#12377715)
Was it Atwood who said, modifying someone else's quote: "The two hardest problems in programming are cache invalidation, naming things, and off-by-one errors?"

Aside from separation of concerns when you make many, many functions, you have to come up with So Many Names.

Re:Why bad scientific code beats code following “best practi... by Gibbon1 on Sunday August 28, 2016 @04:12PM (#12378291)
A lot of those names will end up being the equivalent of nasty old assembly comments.

  add 10   ; add 10 to accumulator.
becomes

  int AddTen(int x) { return(x+10);}