3 ms·
These may simply be issues that are not at the discretion of these developers to either change or discuss with third parties. As tempting as it is to weigh in
by microtherion 6y ago
These may simply be issues that are not at the discretion of these developers to either change or discuss with third parties.
As tempting as it is to weigh in publicly on such matters, the best way for a developer to get results is often to say little in public and try to resolve the issue behind the scenes (as was apparently done here).
- wmf 6y agoThe honest way to handle this would be for the CEO to say something like "I made this decision and I accept responsibility for it".
- eyelidlessness 6y agoAnd the paucity of honesty in public communications is a testament to how few CEOs (and others in a leadership role who could buck-stops-here) are that sincere, willing to take that kind of heat, or to invest in understanding the problem in the first place. It’s also often a testament to how pathologically organizationally shielded they often are; I’d bet money even 5k thumbsdowns on an issue doesn’t bubble up to the top at most orgs.