The Chit Chat Chit Chat Thread

Cesar R M

Well-Known Member
Boss stupidity of today:

Background.. I'm not in charge of some advanced workflows because that has never been my experience NOR MY JOB. I only manage some basic workflows from ANOTHER SYSTEM.

What happened: One of our agency leaders complained that some information was not being displayed in some channels of communications, specific to that agency.
Out of nowhere my boss calls ME to "fix it".
I have absolutely no clue how this workflow works because its not a system I'm trained in and I also did not program it. The irony is that my boss told me to not touch this system because I had "ruined" one of his precious workflows a few months ago.

So begrudgingly I contacted one of the specialists.. and boiii... my boss got incensed that I should not waste hours of this specialist.. you know .. the specialist that PROGRAMMED THE WORKFLOW in the first place.. the EXPERT IN CHARGE of these workflows?
(I assume because of "costs", as this specialist is paid by hour).
I facepalmed but I was like "ok fine, whatever" and made some changes to the workflow hoping that it did work as expected.
Then I asked a third person to check if the changes were correct.
I informed the other agency leader about these and how the workflows are a huge mess of entangled hooks, legacy hooks and workflows between different systems.

And here comes the most stupid thing I've heard from my boss so far..
"Let's focus on making it work, not debugging". WHAT.. THE.. F.....

Note the lovely "LETS".
For those who are IT.... IT guys will know that.... when you test and review something to check for errors, you "debug" and gather information to ensure.. you know.. that the thing.. ACTUALLY WORKS LIKE IT SHOULD.
But no, our fair boss wants us to trigger the workflow, enable it for active unfiltered actions without testing because "IT SHOULD WORK".

:banghead::banghead::banghead::banghead::banghead::banghead:
 
Last edited:

Figgy1

Well-Known Member
Boss stupidity of today:

Background.. I'm not in charge of some advanced workflows because that has never been my experience NOR MY JOB. I only manage some basic workflows from ANOTHER SYSTEM.

What happened: One of our agency leaders complained that some information was not being displayed in some channels of communications, specific to that agency.
Out of nowhere my boss calls ME to "fix it".
I have absolutely no clue how this workflow works because its not a system I'm trained in and I also did not program it. The irony is that my boss told me to not touch this system because I had "ruined" one of his precious workflows a few months ago.

So begrudgingly I contacted one of the specialists.. and boiii... my boss got incensed that I should not waste hours of this specialist.. you know .. the specialist that PROGRAMMED THE WORKFLOW in the first place.. the EXPERT IN CHARGE of these workflows?
(I assume because of "costs", as this specialist is paid by hour).
I facepalmed but I was like "ok fine, whatever" and made some changes to the workflow hoping that it did work as expected.
Then I asked a third person to check if the changes were correct.
I informed the other agency leader about these and how the workflows are a huge mess of entangled hooks, legacy hooks and workflows between different systems.

And here comes the most stupid thing I've heard from my boss so far..
"Let's focus on making it work, not debugging". WHAT.. THE.. F.....

Note the lovely "LETS".
For those who are IT, they will know that when you test and review something for errors, you "debug" and gather information to ensure.. you know.. that the thing.. ACTUALLY WORKS LIKE IT SHOULD.
But no, our fair boss wants us to trigger the workflow, enable it for active unfiltered actions without testing because "IT SHOULD WORK".

:banghead::banghead::banghead::banghead::banghead::banghead:
Make good use of the loaner frying pan:angelic:
 

Figgy1

Well-Known Member
I Love You Hug GIF by Disney Pixar
 

Register on WDWMAGIC. This sidebar will go away, and you'll see fewer ads.

Back
Top Bottom