Let’s start this post with a tune…
29M views – it is just that important.
My day today started with a message from the Padlet Safety Team indicating that they had resolved a case with content on one of my Padlets. They even gave the case number.
Gulp! If that doesn’t wake you up in a hurry, I don’t know what would. After all, I use a Whatever happened? (padlet.com) for people to submit suggestions for my Sunday morning post “Whatever happened to …”. Had something gone wrong? Had I submitted something bad while asleep? Had someone else?
I checked the Padlet out and it seemed OK to me. While I was pondering this, I wandered throughout my mailbox and saw the message again. This is getting strange. I checked out their help page and then decided to respond to the notice asking if it was something that I’d done wrong and should I be learning something from this?
I got a response immediately. Wow, that was quick but it was one of those automated replies to let you know that they got the message. I went about doing some other things and then I got another response from the safety team. The message was comforting as they indicated that there was a bug and it had sent out the original message in error. That made me feel pretty good; it wasn’t me.
But then I thought about other software over the years. I think that everyone knows that you have to have a certain ego element to be a developer which makes it difficult to acknowledge errors. But, I never have had an apology from a developer when I contacted them. That kind of blew me away.
We all know that software is seldom perfect when it is released or sold. If it was every software would be version 1.0!
But to acknowledge that there was a problem. That was really unique and impressive. In my former life delivering workshop after workshop promoting software and tools, we would periodically run into issues. Some of my life seemed to be developing workarounds until things were fixed.
I’d also attended sessions lead by developers as we contemplated implementing something in the system. I’ve got more certifications than I care to admit but you won’t see them as badges here. I think that makes you part of everything that happens including when things go wrong. I even attended a session once where we were explicitly told never to use the word “bug” when referring to an issue that someone might be having. Instead, we were told to say “that’s unexpected behaviour”.
So, I was really struck by the honesty of this reply. I’ve long recommended that people take a look at Padlet to see if it serves a purpose for them. This whole process confirmed to me that the people behind this are honest and open.
You’ve got to like a developer like that.