Here's mine -
We were running on Cloud Foundry, had one DevOps person that mostly dealt with Jenkins, payed for 32-64GB RAM.
Decided to move to K8s (Azure AKS),
Three months later we have 4-6 DevOps people dealing with networking, cross-az replication, cluster size and autoscaling,
And we're paying thousands of $$$ pm for a minimum of 6 64GB VMs.
FAIL
Corporate decided to stop trying to compete with cloud vendors and shut down our in-house Cloud Foundry hosting.
Also Microsoft sales folks worked client decision makers pretty hard.
What? Take some damn responsibility for your decision and stop blaming them on the tools. You solely decided to migrate to K8s while Jenkins was working fine and you solely couldn’t manage a cluster with 6 nodes. That’s your responsibility that the tool you have chosen isn’t fit for your purpose.
In every crowd you will find a set of loud victim blamers.
Take some responsibility for your tools instead of getting defensive worrying that if someone actually yells at one tool author they're coming for you next.
I work my butt off to write good tools and half the time when someone comes to me about a problem, they're still right.
We have a giant Dancing Bear problem in our industry. We sit around hand wringing about all of the bad things people do out there but we never stop to think that it's environmental. Children with fucked up parents become fucked up adults. You surround them with chaos and you get more chaos. You surround them with pain and you get more pain. If you put developers in an environment where garbage tools are not only tolerated but are aggressively defended, what have they been inspired to produce? What can you expect them to produce?
More garbage.
So we go 'round and 'round victim blaming and never owning our part in this cycle of violence.
> In every crowd you will find a set of loud victim blamers.
I think the line has to be drawn somewhere on whether someone is a victim, or are complicit in their own suffering. If someone steps in doggy-doo on a walk, that's unfortunate and they might actually be a victim. However, if someone says "Me and my team have been stepping on doggy-doo everyday for the past 5 months", they are no longer victims, unless someone is coercing them into doing that against their will; and I will have some questions to ask their (technical) leadership.
At any given moment, half of developers have less that 5 years of experience.
I'm not just taking responsibility for my actions, I have to take responsibility for theirs, too. It's expected, but it would be the right thing to do even if it's not. Glitchy, dangerous tools make it difficult to grow other people into senior positions, where they can take responsibility for their own decisions. Every bad tool I use slows the process of creating a peer down.
