2 ms·
The entire point of my first comment was in response to this: > There's a need for a change of tech stack in the company If your company is changing entire te
by bobthepanda 5y ago
The entire point of my first comment was in response to this:
> There's a need for a change of tech stack in the company
If your company is changing entire tech direction, managers should at least be made aware because they will need to plan for time. If this is being run Rambo-style by a few devs going guns blazing for the rest of the company, it's a serious problem, not least because the change in direction might be misguided without a big picture.
> Talking to the rest of the team is a good advice. Traveling the hierarchy up and then down expecting for permission is not.
You seem to be arguing against a strawman.
- marcosdumay 5y agoNobody can be sure there's a need if they don't get to know a better stack. Before management can plan some migration, the technical people must know what else exists and how well it can be used on your environment. After your people run a few replaceable experiments, they can reach management and inform them of the costs and benefits of each choice, but going to management with "our stack sucks, we don't know how to improve it" is guaranteed to lead to a bad outcome, and defending a plan that you don't know how well it will work has a very high chance to turn out bad.