↓ Skip to main content

·107 words

That’s a very astute observation of the state and culture of the Go programming language. I got out of Go way before I hit anything like this (though the Channel Axioms are something everybody is going to deal with). For me Go is a not very interesting intermediary language between Python and Rust.

In particular the crude simplicity is something that I always found suspect. It’s the same you would hear from PHP programmers, “It works, doesn’t it?” If getting something to work is such a feat that you can’t or won’t consider anything more than that, that’s not an environment I want to work in.

https://fasterthanli.me/articles/i-want-off-mr-golangs-wild-ride

Alper Cugun
Author
Alper Cugun

Related

·64 words
“I see operationally-minded engineers working cross-functionally with software development teams to help them grow in a few key areas: making outsourcing successful, speeding up time to value, and up-leveling their production chops.”

·57 words
A lot of the stuff here is our common sense when running projects and also our unique problem as a platform team trying to get stuff done with/for other teams. One thing that engineers tend to forget is how much agency they have: “Although you can’t control what other teams can do, you can influence them.”