4 ms·
Accountability is what you are looking for. This is not a technical problem. Try to find out who is accountable. Who gets fired when the software doesn't perfo
by bombela 2y ago
Accountability is what you are looking for.
This is not a technical problem. Try to find out who is accountable. Who gets fired when the software doesn't perform the way it should. Notice nobody gets fired. Because the whole chain of command is afraid of accountability for themselves.
- hbsbsbsndk 2y agoWho do you hold accountable when all the product teams are choosing their own tech stack and there's no consistency?
- OutOfHere 2y agoThat's good actually. Groupthink and forced consistency are way worse.
- bombela 2y agoIt doesn't matter what they choose. As long as they are accountable for the consequences of their choice. And the company probably pays a platform team to offer a limited but supported tech stack. The platform team is accountable for balancing the deprecation of outdated dependencies and the productivity of their users.
- jjk166 2y agoWho do these teams report to? Either someone at a higher level instituted guidelines which allowed for inconsistent stacks, or someone at a lower level made the decision to disregard these guidelines and upper management took no action at the appropriate time to address the situation. Either decision could easily be justifiable. The higher ups may have deliberately wanted to assure the teams were not stifled, or a team may have had a goal which demanded an exception to the rule. Still though, somebody had to have made the call and should therefore be able to justify it. If an organization does not know who is responsible for something, then that is a failing at an even higher level.
- trentnix 2y agoAccountability is definitely a problem. Now we blame the “process”. The solution to every problem created by the faulty “process” is another bureaucracy, another validation, another tool, or another person in the decision making meeting. And so, everything from Hollywood blockbusters to software solutions is created by committee. The end products are all box-checking, lowest common denominator throwaway garbage. No risks are taken. And very little value is delivered.
- bombela 2y agoNote that if you ask the CEO if you, the owner of a project can be accountable for it. They might say yes quite happily. But when you ask for the power to be able to enforce it, they will refuse. You need power to exercice accountability. Otherwise anybody can come shit in your codebase, and you are now accountable for it. Because you do not have the power to refuse the turd.