spirit-sparrow

My thoughts exactly. :(

DEI programs can be counter productive. The incorrect biases of the past can’t be fixed with opposite biases. Merit based equal representation should be the ideal state. For 10 positions if there are 50 applicants wearing blue and 50 applicants wearing red, knowing that the shirt colour doesn’t matter we should end up ~5 red and 5 blue new starters.

Now if there are only 2 blue applicants, then we should look into if there is something preventing the blues to get to a point where they can apply. That usually doesn’t fall under the hiring company’s control.

I wonder what makes someone go such a great length to bash a language, any language. I say bashing, because even the few valid points in the post are not written in a constructive style. After all is there a language that can't be criticised?

Is the post written to make one feel better having a failed a project the language? (It's not me, it's the language) Or is it the failure to understand that not everyone thinks / works the same and what one finds unacceptably bothersome, others barely notice? Languages that do not cater for a real need would likely vanish on their own, they rarely need help.

As for Go, despite the differences compared to "more sophisticated" languages it works brilliantly for the projects I've encountered. I hope the author is not forced to work with Go though. For the rest of the community, we keep churning out services, giving our feedback to the Go team and seeing the slow evolution of the language without breaking our stuff in production.

That should not be an issue, unless the code is written in notepad. As for interfaces, a better approach is to return struct and accept interface in your functions wherever it is possible.