6 ms·

Depends on your position . I will just tell that my productivity will be decreased if I don't use the one which I believe is best.

by ing33k 15y ago

michaelochurch 15y ago
Dangerous move. Not to say it isn't worth doing, but I've seen it get highly competent people fired. You need to understand that managerial training and experience turns nice people into suspicious, cynical assholes and that you're in danger of being interpreted as threatening, "I'm going to intentionally slow down if I don't get what I want". It's not what you mean, but it's how it will be read. Now, career stagnation, which is what you get if you never speak up, is a lot worse than getting fired, which is surprisingly easy to recover from as long as you have the savings. You just have to be aware of the risks of each avenue. Managers also tend to underappreciate the importance of proper tooling in developer productivity (the commodity developer fallacy) and they tend to view such discussions as "distracting". From their perspective, Java's popularity is a vindication of its value. So many languages and methodologies have been oversold for decades and managers don't know which of these are real (e.g. functional programming, which provides a long-term 2-4x improvement in programmer productivity) and which are bullshit hawked by overpriced consultants. What I've learned is that it's better to use the best tools anyway, deliver software using them, and use existing accomplishments to make your case. Results talk. It's better to ask forgiveness than permission. If you deliver something awesome that helps the company, people are going to overlook what language you used.
- objectatrest 15y ago
  I agree that the best approach is to use a tool and deliver well built software. For every pragmatic tool you recommend some highly paid consultant or senior dev has tried to pad their resume by getting them to buy $100k of unneeded infrastructure and tools that failed miserably. Also, some companies will not budge no matter how you present it you are better off working around the heavy process that is slowing you down. Or switch companies. Or voice you frustrations into the void of the internet like I did. http://objectatrest.wordpress.com/2012/03/27/one-process-two-process-red-tape-duct-tape/ http://objectatrest.wordpress.com/2012/03/27/one-process-two... Each company is different and there is no silver bullet. You need to find out what the managers value (money, productivity, looking good to their superiors) and build a case on that.

Depends on your position . I will just tell that my productivity will be decreased if I don't use the one which I believe is best.

by ing33k 15y ago

Depends on your position . I will just tell that my productivity will be decreased if I don't use the one which I believe is best.

michaelochurch 15y ago

Dangerous move. Not to say it isn't worth doing, but I've seen it get highly competent people fired. You need to understand that managerial training and experience turns nice people into suspicious, cynical assholes and that you're in danger of being interpreted as threatening, "I'm going to intentionally slow down if I don't get what I want". It's not what you mean, but it's how it will be read. Now, career stagnation, which is what you get if you never speak up, is a lot worse than getting fired, which is surprisingly easy to recover from as long as you have the savings. You just have to be aware of the risks of each avenue. Managers also tend to underappreciate the importance of proper tooling in developer productivity (the commodity developer fallacy) and they tend to view such discussions as "distracting". From their perspective, Java's popularity is a vindication of its value. So many languages and methodologies have been oversold for decades and managers don't know which of these are real (e.g. functional programming, which provides a long-term 2-4x improvement in programmer productivity) and which are bullshit hawked by overpriced consultants. What I've learned is that it's better to use the best tools anyway, deliver software using them, and use existing accomplishments to make your case. Results talk. It's better to ask forgiveness than permission. If you deliver something awesome that helps the company, people are going to overlook what language you used.

objectatrest 15y ago
I agree that the best approach is to use a tool and deliver well built software. For every pragmatic tool you recommend some highly paid consultant or senior dev has tried to pad their resume by getting them to buy $100k of unneeded infrastructure and tools that failed miserably. Also, some companies will not budge no matter how you present it you are better off working around the heavy process that is slowing you down. Or switch companies. Or voice you frustrations into the void of the internet like I did. http://objectatrest.wordpress.com/2012/03/27/one-process-two-process-red-tape-duct-tape/ http://objectatrest.wordpress.com/2012/03/27/one-process-two... Each company is different and there is no silver bullet. You need to find out what the managers value (money, productivity, looking good to their superiors) and build a case on that.