“Data-driven” decision: This affects a small number of people, so we won’t fix it.
Values-driven decision: This excludes or harms a small number of otherwise disadvantaged people; that’s not ok, so we’ll fix it.
The metrics you focus on are never neutral.
I'm a believer in "the bug is not fixed until the fix is live", which helps highlight the value of CI/CD.
I'm kind of shocked (and sad) that this integration is rare.
Outside of things like Vercel/Netlify, where have you seen companies publish when changes are live in production? I'm looking for examples of customers opening feature/bug reports, and then having those literal tickets updated when something is live.
I've found product and marketing orgs expect documentation to have funnels when docs users themselves rarely expect, want, or follow any path you provide. Documentation is more like an open air park that people can walk into or through than a carnival with ticket gates and exit
The two most critical assets a company has are psychological safety and institutional knowledge (i.e. the stuff that's not written down). Twitter is now lacking both. 😬
@stevemcghee Fix your code so you can differentiate backend failures. Now that you have data, talk to the backend team about it. Your request patterns might be an outlier for them.
If you're dead inside, go outside. Whether you're taking a walk in a park or hiking in the wilderness, spending time in nature can improve mental health and cognition. Where is your favorite place to spend time outside? Photo by Courtney Celley/USFWS.
Today I explained OKRs and KPIs twice and why you should never mistake KRs for KPIs. My fave example from the two showed how you can apply this framework in your every day life..
One of biggest learnings for me was the importance of architecture to get great outcomes, both in DevOps and in any engineered system.
I was trying to think of a great example of modularity, and started marveling at the USB interface.
Hey, #BookTwitter!
I have been exploring various #books on #DevRel and #community lately. Sharing some of my favourite ones from the bucket list here.📚💗
A thread🧵
@ahidalgosre@niallm Observability (more than just metrics). Consistency, with the goal of simplicity (e.g. "we recommend this pattern..."). Organizational influence (without authority). Dealing with tech debt.
@johncutlefish In Build, @tfadell makes the point that the customer doesn’t care about whatever we call “the product”, they care about their whole experience.
For him, makers should put care into every aspect of the journey. And community is one of those relevant touchpoints.
@josebiro@niallm Doubtful for infrastructure, but we're making progress. Declarative infra and containers are letting us share a simplified mental model, even where the tech leaks implementation details.