Re:Interfaces in Go make it hard to navigate code
by michaelfeathers on Monday May 27, 2013 @05:23AM
(#5774015)
Whenever I read something like this I think that every programmer should be required to spend a significant amount of time working in a large well-written dynamically typed code base. It would certainly help them see that languages and tools are not the culprit when it comes to navigability.
[ Parent
| on HN ]
Re:Interfaces in Go make it hard to navigate code
by pjmlp on Monday May 27, 2013 @07:06AM
(#5774194)
The problem is the "well written" part.
One reason I don't like dynamic languages for large scale applications, is that I have already seen how it works in the world of multi-site enterprise software with outsourcing partners around the world.
The type of companies where unit testing are seen as buzzwords from Silicon Valey startups and are only written if the customer explicitly requires them as part of the contract.
So I am yet to see any "large well-written dynamically typed code" out in the wild, at least in my area of work.
Re:Interfaces in Go make it hard to navigate code
by NateDad on Monday May 27, 2013 @07:22AM
(#5774231)
Outsourcing is the problem here. I've seen some really terrible code written by outsourcing companies, even in static typed languages that are as simple to write as C#. It's not the language, it's the writers.