Resilience is coping with unexpected events and environmental change. To have resilience, you need slack. Slack in software development lets people do the little tasks that keep the work moving smoothly. That helps with everything you didn’t know you needed the software to do.
Can you see a pattern in these examples? SendGrid sends emails for you. You provide it with a webhook URL. It uses the webhook to “call you back” about what happens with those emails, like when they are dropped because your request was invalid. On AWS, you need to listen to an event bus if … Read moreEvery SaaS Integration needs an Upstream Point of Contact
If ya know how to do it, stick with the bureaucracy. If you’re building software, it’s always new — you need a generative org with a resilient structure.
Principles of Collaborative Automation How can we make our tools work with our team? Like a good team member, great tools keep us informed, implement our decisions, and help us understand errors.Drawing from aviation, medicine, and software, here are strategies for choosing and building tools that enhance us and do not frustrate us. abstract Great … Read morePrinciples of Collaborative Automation
(this is a transcription of the talk by the same name. Here is a video.) Collaboration is crucial in software teams – and not only among people. We need our software, our tools, and our automations to collaborate as well. But what does that mean? I have four prerequisites for you here, and then four precautions … Read morePrinciples of Collaborative Automation
The inaugural REdeployConf wrapped up yesterday (as I write this). I’m already feeling withdrawal from intense learning and conversations. I’ll attempt to summarize them in this post. The RE in REdeploy doesn’t mean “again” (lo, it is the first of its kind). RE stands for Resilience Engineering. It is a newish field, focused on sociotechnical … Read moreREdeploy (for the first time)