Adding Correctness Conditions to Code Changes

Today I looked at the first PR on our new project repo. It added a new run script, but the README didn’t mention it. The proposed change was incomplete, because the documentation was out of sync. Did I comment on the PR? heck no. I want to fix this problem for all PRs, not just …

Read moreAdding Correctness Conditions to Code Changes

Every SaaS Integration needs an Upstream Point of Contact

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

Principles 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

Align the stars (programmatically)

Yesterday I was ready to get some changes into master, so I merged in the latest and opened a PR. But NO, the build on my pull request broke.The error was: ERROR: (jsdoc-format) /long/path/to/file.ts[52, 1]: asterisks in jsdoc must be alignedERROR: (jsdoc-format) /long/path/to/file.ts[53, 1]: asterisks in jsdoc must be alignedERROR: (jsdoc-format) /long/path/to/file.ts[54, 1]: asterisks in …

Read moreAlign the stars (programmatically)