4 ms·

I feel this article so hard on so many levels. I've experienced Dante's Enterprise. BUT, regarding what I feel to be a false equivalency - Is Go truly right fo

I feel this article so hard on so many levels. I've experienced Dante's Enterprise. BUT, regarding what I feel to be a false equivalency - Is Go truly right for the exact kind of Enterprise Mush that the Author is describing? Go was invented at Google to solve Google problems is the claim in TFA. And yet, Google is famous for having a very high bar for engineering hiring with a strong focus on CS prowess. So, is the kind of code mush that gets created at Enterprises who put production code written by one-week-of-pluralsight Junior devs headed by analyst-preached-cargo-culting managers - the same as - the Software produced at Google? If not, does Go still fit that former zeitgeist?

kristoff_it 7y ago
Hello fellow lost soul. I don't ultimately know, I think some enterprises are doomed to fail regardless of the technology they end up choosing. In some ways their inevitable doom is capitalism's greatest gift to society, but I've worked in a shop where we had both Go and C# at the same time, and I would have quit way earlier if I had to work on the C# code full-time. Both green-field projects btw.