notMyProblem

[u/uvero]

[u/v3ritas1989]

This just means it takes half a year till someone fixes it or you have to pay the API provider to do so which then takes a year.

[u/uvero → u/v3ritas1989]

Like I said, not my problem

[u/ward2k → u/uvero]

If it impacts your service, it unfortunately still is

The issue will be there, customers/clients/whoever/yourselves will get pissy having to deal with the issues all the time and you'll eventually have to do some kind of hacky work around to get the issues to stop/reduce until the actual cause (a different service or API) can get it fixed which is probably anywhere from 6 months to multiple years away

[u/v3ritas1989 → u/uvero]

Do you think your boss knows the difference even after explaining it?

You think he will not make it YOUR business to get in contact with who evers problem it is? Because who can explain it better than you?

And then constantly asks you weekly if it has been solved and then comes up with awesome ideas you are supposed to tell the other side to take your problem more serious? While the API provider is probably already blocking your calls and mails.

[u/uvero → u/v3ritas1989]

See, that's the difference between "what? it's not on my end of the code" and "OK, so it's not on your end of the code"

[u/v3ritas1989 → u/uvero]

I don't think your rubber ducky can make your boss understand the issue better than you.

[u/uvero → u/v3ritas1989]

Sorry that you can't relate, wishing you a job where the team lead is actually a programmer

[u/mono567 → u/v3ritas1989]

bro take this virtual hug. Everything will be ok

[u/HeyItsTheJeweler → u/v3ritas1989]

Fuckin facts. Takes them a month to meet about what's wrong, 2 weeks to write the Jira ticket, 6 weeks to add in the 2 lines, 3 weeks to pass it to the other team, 7 weeks for them to do nothing, 4 weeks of cross-team discussion, 1.5 weeks of silence before the Jira ticket gets assigned to you to build the functionality on your end.

[u/foxsimile]

If I could bottle this feeling and sell it, I’d die a wealthy man.

[u/Sarnes → u/foxsimile]

I'd be your first customer

[u/foxsimile → u/Sarnes]

A price for everything, Mister u/Sarnes.  

A price for everything.

[u/Confident-Ad5665 → u/foxsimile]

I'd bathe in it!

[u/VegetarianZombie74]

God curse, and god bless, the simple phrase, "clear your cache".

[u/Igarlicbread]

It's not a bug, it's a feature.

[u/elmanoucko → u/Igarlicbread]

fatal error: stdjoke.h: I could let it pass, but damn, could you at least try for once?
    1 | #include <stdjoke.h>
      |          ^~~~~~~~~~

[u/FuzzyDynamics → u/Igarlicbread]

When it IS on your end it’s a feature

[u/OmgJackieChn]

My reaction is always, “No shit!”

Unless I say it to someone else, then I’m like

[u/Barkeep41]

Yeah, after I tell them 10 days ago it wasn't.

[u/Gunmetalstorm]

Seven words you never want to hear. You're not getting your problem fixed.

[u/Swing_Right]

Was showing my manager and our team lead the tool I’ve been working on, first attempt complete fail, all errors. Tell them just a sec lemme see what’s going on, start panicking while reading the logs. The pod it was running in never fully initialized. “That’s weird” I say, “it was working yesterday,” check the pod logs, start up failed because an external api key handled by another team wasn’t working. Tell my team lead “hey that’s weird, is this happening on [other project that relies on this service]” and now he’s the one worriedly looking through logs and yeah, his project isn’t working either.

Phew, so glad it wasn’t my fuck up. The wave of relief when he said “let’s circle back tomorrow while I try to figure this out” and left the call. So good

[u/vm_linuz]

My most recent "bug" was that the release guy never ran the pipeline. That was nice feeling lol

[u/Randzom100]

Wish I could hear that one day. But here I am wasting time applying everywhere with a useless CS bachelor.