We sometimes use this in retro's, to drive discussion about what's working and what isn't by putting Red/Amber/Green votes next to the sections then discussing what's lacking. It's great for framing the discussion
We made this because although the right thing to do varies from client to client (and YMMV), we needed a starting point to say, "this is an example of good", particularly when bringing in new people, and talking to clients
Awesome, the cheat sheet I helped make with a bunch of other @ArmakuniHQ@twitter.com'ers of sensible defaults to to setup a high performing team is now GitHub https://github.com/armakuni/ak-way-cheatsheet
I keep being tempted to create something that parses HAR files generated by a proxy and runs them through OPA. But it feels like one of the things I'll try then get bored of maintaining
(Zap is what I usually end up using but it's not great, tends to be flakey and meh, also it's slow and uses a lot of resources)
Maslow’s Hierarchy of Needs and Blackfoot (Siksika) Nation Beliefs - https://barbarabray.net/2019/03/10/maslows-hierarchy-of-needs-and-blackfoot-nation-beliefs/
"For example, one study found that simply using rudimentary tools for navigating code (scroll bars, text search, etc.) can account for *up to a third of the time* spent debugging code."
Never discount the importance of developer tools. 🛠️
https://www.apress.com/gp/book/9781484242209, via @email@example.com
That is just the ones we know of, the real numbers will be much higher
preview for a zoom talk I'm giving in like seven and a half hours
I'm helping @firstname.lastname@example.org work again today. I like helping. Yesterday I even got to help @BillieCodes@twitter.com work.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!