Encountering problems and making mistakes is a consequence of life, business, and everything else — and unavoidable. But the value is in how you respond to them.
As I said on Twitter this past week:
I’ve found that the best lessons in life — by far — are those where you learn how NOT to do something.
But still, as good as vicarious experiences are, they only get you so far.
In the beginning, there was the mistake…
By gum, was it a doozy! I’ll spare you the gory details (because they are — for the most part — irrelevant) but it was less a bug and more an infestation in the code. In the grand scheme of things, it has caused problems for our schedule, but the Under Cloud remains on course.
Stripping the whole problem down and tracing it to its source, it was — as these things often are — a failure to communicate, which resulted in team members and myself labouring under the assumption that something was when it wasn’t.
And then came the procedure…
So how did I respond?
We’re using a number of things to manage what we do. As a team of 3, we don’t need a lot, but we find that Slack and Trello are enough to keep things together, although we often find things said and done become lost inside the whirring cogs of the communication machine!
I created a list in Trello and added a card entitled: “Deprecated”, within which I wrote the following description:
“Here are all of the parts, components, and libraries of the application that have been deprecated, and what they’ve been superseded with.
Please update this card as and when required, but also refer to it, too!”
Some might argue it’s just a patching of holes, while some might claim it’s only of any use if people follow the procedure, but I would counter by saying that’s life, business, and everything else…