undefined | Better HN

0 pointsClosi5y ago0 comments

I assume one of the use-cases for this is that they found a bug, quickly fixed and wrote a test case, and then pushed it to Git without raising a ticket themselves and then solving the ticket.

With an 8 person team all sitting together, someone can just shout across the table and ask someone else to resolve an issue without raising a ticket too. Are you solving ticket A but need another person to help you with a bug you discovered in the API that the person across from you wrote and can fix in 2 mins? Sometimes they just do it and don't raise a ticket. If management likes to mark you on tickets, you might as well raise the ticket.

I work at a big company, and every time the IT Helpdesk does a password reset they open a ticket, then mark it as closed, every time they do a password reset (because they get marked on how quickly they close tickets). Believe it or not, median resolution time for a raised support ticket is in seconds, despite it usually taking days if you open a ticket for anything yourself!

8 person teams are usually the recommended max team size anyway under Agile (two pizza team).

0 comments

3 comments · 1 top-level

ogre_codes5y ago· 2 in thread

> someone can just shout across the table and ask someone else to resolve an issue without raising a ticket too.

I rarely see my team-mates in person at the moment to shout at them. If I did, they would likely tell me to fuck off because they are busy with some other task. The only sort of issues where it's appropriate to drop what you are doing and immediately fix it are the most severe issues which need to be fixed right now.

> I work at a big company, and every time the IT Helpdesk does a password reset they open a ticket, then mark it as closed, every time they do a password reset (because they get marked on how quickly they close tickets).

In general, if documenting an issue (of any sort) is more work than resolving the issue, you shouldn't bother documenting it.

But as a developer, many of those easy to fix issues are found by people who don't have the skills or resources to fix them. The best way for someone to communicate those problems is usually some kind of ticketing system.

ClosiOP5y ago

> If I did, they would likely tell me to fuck off because they are busy with some other task.

Great team dynamic if one of the members is blocked or has an issue because of something that another person wrote, and they get told to fuck off.

ogre_codes5y ago

So... "shouting across the room" for a ticket which is so trivial it doesn't need to be documented is OK, but telling someone to "fuck off" for doing it is not?

Your priorities are backwards. I would not work at a place where interrupting me during coding to fix a trivial bug is considered acceptable.

1 more reply

j / k navigate · click thread line to collapse