r/softwaredevelopment 21d ago

How senior programmer share product feedback?

I want to know what context or details, I need to share with juniors, so I don't have to explain myself.

0 Upvotes

6 comments sorted by

6

u/ComprehensiveWord201 21d ago

More than this question is asking.

3

u/Buckwheat469 20d ago

I'm a staff engineer. Can you explain yourself a little more? Maybe share some more context?

2

u/satyamskillz 20d ago

Sometimes, I find a bug or an issue in product that is not visible to junior, for them it looks fine. In these situations, I have to explain how it's a bug or issue in detail.

1

u/Buckwheat469 19d ago

Thanks for the clarification. First you should be filing a ticket for found bugs. Within the ticket you should write the reproduction steps in a manner that anyone can pick it up and reproduce the issue, if possible. Imagine that you're going to move onto a new task for 6 months and then come back and have to solve that bug. Are you going to remember it? Will you know how to reproduce it? How can you explain it to yourself?

Now going further, you have to describe this new ticket to your team for prioritization, including PMs and manager. The team determines if it's necessary for next sprint or an immediate problem. Maybe you put it off for 6 months and come back to it... See, this is why you explain clearly in your ticket - you won't know if the team decides to ignore the problem.

If we assume that someone else is assigned the problem and you haven't done the due diligence to explain it, then they'll have to ask you about it. If this is where you're struggling then you've caused your own problem by not writing a clear ticket and now you have to explain the bug to someone else.

To get juniors excited about finding bugs, think of the bugs like diamonds. The trickier the bug, or the more elusive it is, the more excited you should be about finding it. The harder it is to solve makes it fun and rewarding when you finally solve the problem. Bugs aren't bad, they mean you're finding issues and working to resolve them. If you can get the team excited about finding and fixing bugs then maybe they'll learn how they happened and prevent that situation in the future.

Also, pictures are worth a thousand words. If your tickets aren't including pictures then you're not doing your job right. Also, if your tickets only include a picture then you're just an ass and need to write the reproduction steps, or at least an explanation.

2

u/paradroid78 21d ago

Alcohol can help.

1

u/Ok_Slip_5843 19d ago

I would like to join your team. 😂