7,137 karma · joined October 26, 2011
I think this whole article/title is ragebait at best.
https://www.huckmag.com/article/yusuke-nagata-photographer-d...
Money doesn't fix any of our problems either, even if you're one of the few lucky to have enough of it, you can't possibly be happy living society perpetually decaying. We'll always be as happy as our neighbor.
As the author of https://github.com/ahmetb/go-linq, it's hard to find adoption for libraries offering "syntactic sugar" in Go, as the language culture discourages those kind of abstractions and keeping the code straightforward.
So it falls on a tech lead to point out who are the sailors in the ship that are not rowing (or worse paddling backwards). I'm not saying "go build a git commit counter dashboard" but if you're working with dozens of people and it appears someone isn't delivering a lot of work lately, it helps you double check your assumption. (Again, not saying commits are a good metric.)
This blog post is definitely relatable to most of us because we join teams that are somewhat dysfunctional, and if you have the influence capital and the chops to turn that team into a place where hiring is done properly, people have motivated and the right amount of work and the room to grow, I think you can turn the ship around. Or maybe I'm too naïve and have a lot more to learn.
This is most obvious in Kubernetes, where you have a list property like:
"conditions": [{"type":"a", "status":"b"}, {"type":"c", "status":"d"}, ...]
and you can't really create a patch like "change the conditions[type="a"].status to foo". As a result, you usually end up doing a whole field patch.