Don’t say “I found a problem.” Say … “I found a problem, here’s a solution .. and proof.”

A few things have not changed in the age of AI, where the LLM has replaced 3/4 of the brain power of a whole generation of engineers who once found their meaning in the code they wrote. I mean, I hate to say it’s true, but a lot of folk should have been finding their meaning in the code they decided NOT to write. It’s the classic mix-up of smart engineers and developers thinking that their “use” or “importance” to a company or product was the amount and cleverness of the code they put out. They worshipped at the feet of their own fingers, enamored with staring at themselves in the mirror, convincing themselves they were smarter and could write better code than those around them.

Having worked with and met many such folk, this has sadly never been the case. In fact, there is probably an inverse correlation between people who saw themselves as the smartest person in the room because of their clever code, and their usefulness to the overall team and company.

Anywho, back to the matter at hand. Problems.

What do you do when you find a problem, what we like to call “bugs” in the biz. Software biz that is. Here are the standard responses from 80% of the hobbits out there.

• I found a bug.
• I found a bug. I’m going to find out whose fault it is.
• I found a bug; you should be worried about this.
• I found a bug; the sky is falling.
• I found a bug; how do I fix it?
• etc.

None of these are really novel or helpful at all. It would probably be better to simply go back to a time, like 5 minutes ago, when the bug existed, and we were all caring on our day in perfect bliss. That’s the point, you see. Look, I’m not sure how long you’ve been around tech, writing code, or whatever it is that you do. I have a very special secret to tell you; promise me you won’t spill the beans? Ok.

There are bugs in most software. Syntax bugs, business logic bugs, just bugs.

Some are sneaky, some are new since the last few PRs went in, some are old, having been around for years. Some become bugs when the business logic changes. Doesn’t really matter; bugs are a part of life (software) for better or worse. They are here; it’s part of our job to fix them.

Did you catch that last part? Fix them. That’s part of our job. To fix bugs. Did you get it? Fix them. I get that some places, like their retros, you know, get everyone in a room and say the word “blameless” a few dozen times while we make someone squirm in their chair for an hour, getting all sweaty, hot, and bothered.  Yes, yes … of course there are lessons to be learned; we all need to learn our lessons.

Another secret for ya, again, don’t tell nobody. Guess what your C-suite has a lot of? Problems. CTO? Problems. Your boss? Problems. That cranky dude over in Product? Problems. Heck, your coworker a few desks or Slack channels down? Probably milk thrown at ’em by some toddler this morning, is stressed about the next mortgage payment. They got problems. You got problems too Sunny Jim, don’t lie. You know what we don’t need more of? Problems.

Bring solutions, not problems … and data.

So, break the mold; don’t live in a problem-focused world. You found a bug. Congrats. Call your mom; I’m sure she will be proud of you. I’m not. Neither is anyone else. They don’t want more problems; heck, you don’t even want your own problem you found if you really think about it. But, nevertheless, here we are; you found another bug. Now what?

We should reframe the entire conversation; that’s what we should do.

You didn’t find any stinking problem. You found a solution and some data to back it up; that’s what you did. There wasn’t even a problem; call it an issue. You found a small issue, but that’s not the headline; the headline is that you found a solution to this issue, you got some data together, and look here …

• We have a solution that is x or y complex.
• The change looks like z.
• The data says this is the impact.
• This is who is affected by this issue and the proposed fix.
• This is the downstream impact.
• Here are a few options we have.

Again, we didn’t find a bug. We don’t care THAT much about how it came about; we are here now. Heck, it isn’t about the bu…. I mean issue. It’s about the solution(s); maybe we have a few ways to improve the process, a few different technical solutions, and some data ready for the Product or CTO to look at to keep them in the loop. People like being in the loop, especially when the issue provided has ready solutions, impacts, and data waiting on a platter for them to dine on, to sup on, wow … you aren’t the problem person … no no, you are the Solution Person.

• The data gives the folks confidence that you know what you’re talking about, and we can agree on the solution(s).
• The ready-set-go solution(s) provided for the issue can be chosen within minutes, as a matter of preference.
• No one gets heartburn about another Slack message from you about a bug.
• The sky isn’t falling.
• We are moving everyone and everything forward, not stuck in the past.
• Progress is being made.

I hope I wasn’t unclear. Do yourself a favor: start thinking not in terms of I found a problem or bug, how many people can I tell and stress out in a single nasty Slack message … but rather … wow … I found an issue and I think I have idea of the perfect set of solution(s), and while I’m at it, let me throw some data together to prove the point and show everyone what’s going on and how we are moving forward with confidence.

Look, you want to witch hunt the idiot (50% of the time it will be you) that dared to be human and created a bug? Fine, have fun; I’m sure everyone will just love you for it. You will do well in your career there *insert eye roll. But you’re living in the past when you do that. You are attaching, intentionally or not, negativity to yourself. You become synonymous with that bug or problem, created by you or not. In others’ minds, they have pain when they get a problem with no solution, and if you bring that pain, you are the pain.

Worried about your job with all those Agents running around convincing CEOs to lay everyone off? Then don’t be the problem. Be the solution.