Grissallia 🏳️⚧️ on Nostr: A little professional story: Please be kind when "correcting" co-workers about ...
A little professional story:
Please be kind when "correcting" co-workers about something you feel they've misunderstood or are just wrong about.
One of the really weird things in my life is that I seem to encounter -or trigger- edge cases.
For non-technical folks: an "edge case" is a generally rare bug that only occurs under a very particular set of circumstances, usually quite obscure.
Someone might report a bug that no-one can reproduce, and it turns out that the bug only occurs on the last Friday of the month, if the device is used between 9pm and 10pm. We refer to something like that as an "edge case".
A few years ago I found a *really* weird bug in one of our products, and I mentioned it to one of our senior developers.
That person then proceeded to loudly, and in front of an entire group of co-workers, lambast me for something that was OBVIOUSLY end-user error, and was "fundamentally impossible" to be anything else.
It was one of the most humiliating professional experiences of my life.
It made me incredibly wary of raising Jira tickets, unless I could fully reproduce and document a bug.
A couple of years after this incident, I was chatting with another dev who'd started working with our company, and was in QA, and he mentioned this edge case he'd recently encountered.
If condition A, and condition B, and condition C, AND condition D were all met, it would trigger this really weird bug.
...the same one I'd mentioned to one of our senior devs a couple of years earlier. It wasn't end-user error. It was an edge case.
[sigh]
Yesterday during our weekly technical meeting, I asked a question as to whether an underlying software process had been significantly & quietly changed recently.
I explained that I'd encountered a number of weird incidents over the past couple of months, but nothing I could log or document, just that I had a gut feel that there's a intermittent bug in play, and that after my 15-hour day on Wednesday, I was now almost certain that changes might have occurred in that particular process.
Turns out that entire process had been rewritten.
I was asked why I hadn't raised any Jira tickets for it.
Our dev team could have had a couple of months headstart on this issue, and documented occurrences of it, if a deeply frustrated and under-pressure dev hadn't publicly ripped me a new arsehole five years ago.
Everything is copacetic. No-one is upset with me, the dev who asked me why I hadn't raised the ticket was the QA dev, and all I had to say was "Bug X", and we both laughed, and the dev team gets more of my "gut feel" bug reports moving forward.
The other dev and I are on excellent terms these days as well. I went to the mat with them three years ago, and they apologised, and we talked out our differences, and we have a great working relationship now.
How you treat people matters, even in a moment of deep frustration, and can have long-term consequences in ways that you may not expect.
Be kind. Always.
Please be kind when "correcting" co-workers about something you feel they've misunderstood or are just wrong about.
One of the really weird things in my life is that I seem to encounter -or trigger- edge cases.
For non-technical folks: an "edge case" is a generally rare bug that only occurs under a very particular set of circumstances, usually quite obscure.
Someone might report a bug that no-one can reproduce, and it turns out that the bug only occurs on the last Friday of the month, if the device is used between 9pm and 10pm. We refer to something like that as an "edge case".
A few years ago I found a *really* weird bug in one of our products, and I mentioned it to one of our senior developers.
That person then proceeded to loudly, and in front of an entire group of co-workers, lambast me for something that was OBVIOUSLY end-user error, and was "fundamentally impossible" to be anything else.
It was one of the most humiliating professional experiences of my life.
It made me incredibly wary of raising Jira tickets, unless I could fully reproduce and document a bug.
A couple of years after this incident, I was chatting with another dev who'd started working with our company, and was in QA, and he mentioned this edge case he'd recently encountered.
If condition A, and condition B, and condition C, AND condition D were all met, it would trigger this really weird bug.
...the same one I'd mentioned to one of our senior devs a couple of years earlier. It wasn't end-user error. It was an edge case.
[sigh]
Yesterday during our weekly technical meeting, I asked a question as to whether an underlying software process had been significantly & quietly changed recently.
I explained that I'd encountered a number of weird incidents over the past couple of months, but nothing I could log or document, just that I had a gut feel that there's a intermittent bug in play, and that after my 15-hour day on Wednesday, I was now almost certain that changes might have occurred in that particular process.
Turns out that entire process had been rewritten.
I was asked why I hadn't raised any Jira tickets for it.
Our dev team could have had a couple of months headstart on this issue, and documented occurrences of it, if a deeply frustrated and under-pressure dev hadn't publicly ripped me a new arsehole five years ago.
Everything is copacetic. No-one is upset with me, the dev who asked me why I hadn't raised the ticket was the QA dev, and all I had to say was "Bug X", and we both laughed, and the dev team gets more of my "gut feel" bug reports moving forward.
The other dev and I are on excellent terms these days as well. I went to the mat with them three years ago, and they apologised, and we talked out our differences, and we have a great working relationship now.
How you treat people matters, even in a moment of deep frustration, and can have long-term consequences in ways that you may not expect.
Be kind. Always.