3 ms·
Your enthusiasm for new tools and the energy with which you embrace change is great. Don't lose that. But it's no fun to try to use something, and you can't be
by stephengillie 11y ago
Your enthusiasm for new tools and the energy with which you embrace change is great. Don't lose that.
But it's no fun to try to use something, and you can't because someone moved fast and broke things. It's even less fun when your customers are calling you because your site is down, and all you can say is "It's a problem with the platform." Before long, you get to choose between the platform you're paying for, and the customers who are paying you.
- studentrob 11y agoAll these comments are one-sided. Note that gravity13 said "if done correctly" There are pros and cons to adding new tools. Each situation is different and would ideally be decided by all the effected team members. It depends on the team, existing tools, product, whether it is released yet or not, and a myriad of other things. An engineer could install whatever he likes on his own machine or VM in his free time, if he has any. If other engineers have a problem with that, then like gay marriage and abortion, that is their problem. Similarly, if an engineer installs software willy-nilly on a production machine that has active users, I think we can all see how that is unreasonable. So the debate comes down to the in-between grey areas. Without being in the moment, none of us can comment on it towards any real conclusion.