Probabilistic programming does in 50 lines of code what used to take thousands

Re:Probabilistic programming does in 50 lines of code what u... by mafuyu on Monday April 13, 2015 @03:28PM (#9369831)

It makes sense to talk about lines of code when thinking about engineering hour efficiency. It costs the same amount for a programmer to write one line of C as one line of Assembly, and the rate of bugs tracks lines of code as well. The underlying libraries and abstractions should be considered if you're thinking about computing efficiency.

[ Parent | on HN ]

Re:Probabilistic programming does in 50 lines of code what u... by choward on Monday April 13, 2015 @04:00PM (#9370053)

Using lines of code as a metric makes no sense at all. Bad programmers produce more lines of code. Does that make them more efficient?

[ Parent | on HN ]

Re:Probabilistic programming does in 50 lines of code what u... by mafuyu on Monday April 13, 2015 @04:03PM (#9370069)

A good programmer that writes less lines of code is more efficient than a bad programmer that writes more to do the same work, because you pay each per line of code. A library that allows both to write less lines of code will increase efficiency for everyone.

[ Parent | on HN ]

Re:Probabilistic programming does in 50 lines of code what u... by Retra on Tuesday April 14, 2015 @12:27AM (#9372106)

The time it takes to learn and master the language aren't irrelevant either.

[ Parent | on HN ]