Subj : Re: Project Meetings
To   : Commodore Clifford
From : Bf2K+
Date : Tue Dec 26 2023 10:12:24

On 22 Dec 23  12:40:16 Commodore Clifford wrote...

CC> On 21 Dec 23  16:06:00 poindexter FORTRAN wrote...
CC> 
CC> PF> -=> Commodore Clifford wrote to Nightfox <=-  
CC> PF> 
CC> PF>  CC> My favorites are the ones where we have a four hour meeting
CC> PF>  CC> to discuss an incident, listening to someone prattle on
CC> PF>  CC> about how they want to be "fair to the devs"... in the
CC> PF>  CC> meantime, the problem isn't even with our code, but with
CC> PF>  CC> another system entirely and once the correct people figured
CC> PF>  CC> it out, I doubt it even took that long to fix it.  
CC> PF> 
CC> PF>  I remember a prticularly spicy post-issue meeting after my
CC> PF> company's  web site was down for an extended period. teams were
CC> PF> trying to find the  root cause, our DB said it wasn't the DB, and
CC> PF> when he was questioned  further, he quit, because he wouldn't
CC> PF> work somewhere where his  expertise was questioned.
CC> PF> 
CC> PF>  If memory serves, it was the DB. 
CC> 
CC> To which Commodore Clifford replies...
CC> 
CC> In my case, we have the opposite problem.  We have our huge meetings
CC> when something goes wrong and they always blame us and want us to
CC> "own" the problem because it's on the website where you see the error.
CC> 
CC> The problem is, it's rarely really our problem when it's something
CC> big... it's usually one of the hundreds of service endpoints we have
CC> to interact with.  One of those fails, we have an error message
CC> displayed. But it's not our code that is in error.  Sometimes, we can
CC> do a fix faster (this is usually the case when someone makes a change
CC> to a service without actually testing it or notifying all consumers
CC> of the service) but they still try to "blame" us.
CC> 
CC> It's getting old.
CC> 
CC> --- RATSoft/FIDO v09.14.95 [JetMail 1.01]  * Origin: STar Fleet HQ -
CC> Real Atari! bbs.sfhqbbs.org:5983 (21:3/171.0) 

To which Bf2K+ replies...

Whenever my customers have an issue with a 3rd party device, we ahve to
go in and solve the problem.  They ahve no understanding of the Siemens
PLC controlling the machine, so every little problem is blamed on Siemens
and we have to fix it.  This happens 80% of the time... it is downright
stupidity.


--- RATSoft/FIDO v09.14.95 [JetMail 1.01]
 * Origin: STar Fleet HQ - Real Atari! bbs.sfhqbbs.org:5983 (21:3/171.0)

.