3 ms·
>...really shouldn't almost the entire focus be on the terrible design and the people responsible for it in the first place? I was just thinking that! I can j
by scoggs 9y ago
>...really shouldn't almost the entire focus be on the terrible design and the people responsible for it in the first place?
I was just thinking that!
I can just imagine (in my own head, of course) that this guy has been banging pots and pans talking to executives and those above him to set aside the time and/or budget to fix the terribly archaic and sensitive system. Now he's sitting there looking guilty as possible and his only way out is to throw everyone who ignored him under the bus.
Why do I assume that things are this way? I feel like I've dealt with 20-30 different situations like this in my ~12 years programming and of course they were WAY smaller in comparison but there is no "clean way out". Feelings are going to get hurt and the work place's fabric could be torn to shreds. Nobody wants to be responsible for that.
- continuational 9y agoThat’s just bad leadership. Leadership is about taking responsibility. “Here’s what happened, here’s what we learned, and here’s what we’re doing to make sure it doesn’t happen again.” It’s doesn’t have to end badly for anyone.