Making the move from Scala to Go

Re:Making the move from Scala to Go by lacampbell on Wednesday January 25, 2017 @01:10AM (#13479088)

That's why I'm a proponent of code ownership. We should be coding to each others interfaces instead of constantly poking around in the same shared codebase. It just leads to pointless re-writes and low quality - a tragedy of the commons.

https://www.visualstudio.com/en-us/articles/devopsmsft/code-...

[ Parent | on HN ]

Re:Making the move from Scala to Go by jiaweihli on Wednesday January 25, 2017 @02:03AM (#13479354)

Unfortunately sole code ownership increases the bus factor.

[ Parent | on HN ]

Re:Making the move from Scala to Go by lacampbell on Wednesday January 25, 2017 @02:13AM (#13479396)

Why? The code is still there even when a person leaves.

[ Parent | on HN ]

Re:Making the move from Scala to Go by enqk on Wednesday January 25, 2017 @02:33AM (#13479493)

Code is really hard to work with without the theory that surrounds it, and is alive in the people who worked on it.

Peter Naur - Programming As Theory Building http://pages.cs.wisc.edu/~remzi/Naur.pdf

[ Parent | on HN ]

Re:Making the move from Scala to Go by lacampbell on Wednesday January 25, 2017 @03:14PM (#13485545)

Legacy shitcode is legacy shitcode. If it's owned by someone at least we can push for a sane interface, which is better than the abandoned communal messes I encounter in the real world.

[ Parent | on HN ]

Re:Making the move from Scala to Go by enqk on Wednesday February 01, 2017 @02:15AM (#13538979)

[ Parent | on HN ]