A friend asked me recently what I think the big things are that make GCP, Azure, and AWS different from each other.
I think the biggest thing is how they view customers.
The highlight of my week: a guy came up to me and said he showed his leadership team my salary demands tweet and was able to get his *entire team* raises. I love helping people get paid what they’re worth and more 💜💜💜
What was the best thing your company did during onboarding?
When I onboarded my manager put together a Trello board with a column for each week. Each week had cards for different tasks. I also had a pipeline with cards introducing each team member!
I still hold the strong opinion that every company should have a team that teaches new hires how to be experts in the primary tools used at the company (e.g. Gmail, Slack, Docs, Jira, Notion). And I'm not talking a few keyboard shortcuts here and there. I'm talking top 1%.
If 1), hand them a copy of Accelerate. https://t.co/MHkf5ItV3T
If 2), you probably need to surface more information about the facts on the ground, and you need to do it in a way that is *specific* and *actionable*. Moaning about how everything is fucked is not going to help.
So if you keep losing the battle to pay down your infra investments and actually fix things, consider two possibilities:
1) they don't understand why backend/reliability work matters,
2) they do understand, but aren't getting enough of the right signals to make good decisions.
🎉I'M SO EXCITED🎉 I can finally share that DevOps Handbook 2e is coming soon, and I'm an added author. We've updated with new cases and (ofc) updated data.
These kind of forced marches (w/the broken families and divorces mentioned in the next tweet) are why I started doing my research— because there had to be a better way to build SW w/o breaking people.
Turns out, there is.
Everyone sensible in IT has been saying for years that if you buy COTS (commercial off-the-shelf software packages) you shouldn’t customize it - it’s wildly expensive and you end up with something hard to maintain and almost impossible to upgrade.
I teach a graduate level class on OO and TDD and every year I get upset because I have undergrads in my class who have been taught that encapsulation means adding getters and setters to your classes 🤬🤯
@johncutlefish There's a phrase I use a lot when teaching other PMs - "Everything you do as a PM is an opportunity to collaborate and build trust."
That includes writing tickets/stories.
For me it was @jasoncwarner who told me that we need more empathetic leaders in product management, then took a chance on me to help run his product team. Gave me enough room to work autonomously and be curious about what we could accomplish together.
Or... A burndown chart is a simple way to cling on to 30-year old legacy Tayloristic practices, micromanage your team, create undue stress and emphasise unfit for purpose approaches rather than what's actually important in the complex, value-driven domain of product development.
I think the most challenging part of management is recognizing that the people you manage are different than you.
They have different goals, aspirations, motivations, styles, everything.