@xenograg @justinph@nytimes Apologies for all the git blames along the way🙂 Back when Backbone.js was the tool of choice. The new tech seems to work great from what I can see. ❤️
8/8 If you are a leading a team in a situation like this, be kind and seek the truth. Your team, company, and customers will all benefit from doing so.
Update on cloud outage impacting ~400 customers. As part of scheduled maintenance our team ran a script to delete legacy data from a deprecated service. Instead of deleting the data the script erroneously deleted sites, and connected products, users, and 3rd party apps. (1/5)
7/8 Many of us software developers and leaders have a vivid memory of breaking the production environment in some way that caused us to panic. It’s what happens after the event that makes us remember it with either dread or a valuable learning experience.
The Senior IC path is probably the best thing that's happened to management.
Forcing reluctant people into managerial roles has caused so much workplace trauma for everyone.
@nicksrockwell@sfelc_ It was nice to hear a familiar voice on ELC! Really enjoyed listening to you discuss the transition away from heroics around incidents.
tips for being a kind coworker (aka how to not be an asshole)* 🧵
* not a subtweet, I swear
1. a classic: don't feign surprise (h/t @b0rk https://t.co/IX4Q4MLGqE)
@SketchHelp When trying to add a new account on our team, the "Join" button we get in the email is just taking us back to the sign in form without any details for creating an account. Can you help?
We think Blameless Postmortems are really important to innovation on our engineering team. Here's a pitch for why you (and the rest of your organization) should use them too! https://t.co/LzIp8Kqoup
@jonjoden@nicksrockwell I was just thinking about that this morning. I can only imagine the number of requests that varnish was tearing through. Awesome response times... amazing stuff!