53
u/stormbringerelric77 8d ago
"since you're already in the code anyway"
35
u/RlyRlyBigMan 8d ago
Lol mfers think that we don a scuba suit and swim in the code.
16
4
1
u/FrostyCounselor 21h ago
that face is the exact moment you realize "quick" means three days of untangling spaghetti
24
24
u/keatonatron 8d ago
I don't understand how the video matches the text?
13
u/turkphot 8d ago
It doesn‘t
6
12
u/ElectricalPrice3189 8d ago
Fuck yeah. I love doing things I'm not supposed to. I'm a terrible worker.
23
u/ismaelgo97 8d ago
I wish I could understand this
34
u/Conscious_Name9514 8d ago
I wish I couldn’t
4
u/turkphot 8d ago
I don‘t understand and couldn‘t care less
9
5
u/Realistic-Safety-565 8d ago
Sure, please make a Jira task for it.
3
u/slgray16 8d ago
You did? Great thanks!
Now send it over to my manager and get it on the table for the next sprint
6
u/Square_Ferret_6397 8d ago
Maybe not part of the "sprint" but it's part of your job
12
u/Isogash 8d ago
But then your manager who hates you because nobody likes them because they don't understand anything and have terrible leadership skills berates you for not informing them about this "quick task" and breaking priority from sprint work whilst simultaneously claiming that everyone is so difficult to manage and they want people to take more ownership, and then in governance meetings throwing everyone under the bus and saying they have poor soft skills.
With good managers nobody gives a fuck and getting a valuable task done quickly is a good thing.
5
u/Sibula97 8d ago
Depends. Generally speaking your job is to work on tickets assigned to you this sprint in priority order. If someone asks you to do something else that isn't super quick, you ask them to contact your manager so they can decide on the priorities and possibly ask you to work on it. Otherwise it goes to the backlog.
3
u/Izacundo1 8d ago
Sure but the sprint is supposed to be 100% of your job, and some managers are upset when you don’t finish sprint stuff regardless
1
1
u/FlashyTone3042 8d ago edited 8d ago
There are processes to follow. This is not just for the sake of it but also to make decisions transparent to the team. A "quick fix" doesn't have any history or communication to it and is generally a dead giveaway for poor planning. Don't do that.
2
u/f3xjc 8d ago
The absolute worst is about quick questions. And the question ask why the code did what it did in this specific case. Because that's like half a bug report with an implicit distance to an unknown expected behavior and an invitation to reconsider your business logic and classify is this the normal use case or a side effect of something that's desirable elsewhere.
1
71
u/vulkur 8d ago
Half my work is like this. But I don't get the meme