41–47 of 47 posts
If this isn't obvious to your use case, there is no business reason for trying a new programming language and you are doing the whole business a disservice. I should never have to sell a new language or technology. If it's something the business needs, the uses will be obvious.
If this isn't obvious to your use case, there is no business reason for trying a new programming language and you are doing the whole business a disservice. I should never have to sell a new language or technology. If it's something the business needs, the uses will be obvious.
Thinking that something sells itself is an engineer's mistake. I'm an engineer myself, and I have learned through experience that quality is not enough. Selling is important.
- Will using lang X over Y reduce total lines of code? That's less work, less time, less money.
- Are # jobs for lang X rising? Show some pretty graphs. We can't fall behind the market.
All of this is bullshit to an engineer, but precisely how you need to sell it.
Earlier quoted context omitted.
A screen capture sounds like a very good idea, as a nice way to visualize. People tend to buy based on emotions, and then rationalize with logic. The screen capture sounds like an appeal to emotions, while "the NASCAR slide" would work as justification.
The "NASCAR slide" can also appeal to emotions, as a form of peer pressure. "Oh I wanna be like the big guys, and the big guys use this, I should do what they do".
You'd be surprised how often competitors (let's say BP and Shell for example) make purchasing decision after discussions at user group events, simply "to keep up with the Jones's".
So, to begin, this is really hard to do, and it can lead to the end of your career at a place. Managers might think of you as That Guy, the one who is always coming out with disruptive ideas. ("Disrupt" ain't a positive term, here.) That Guy makes the manager's job harder because the manager wants a unified front, not debate. 1. It helps if the language interoperates well with the existing platform. If you're at a Ja…
That's an important point. It's going to be a lot harder to convince your company to make changes that require major work on the operations side, since those kinds of changes need to cross more departmental or political boundaries. Moving from C# to Clojure would be much harder, since if your company has been using C# exclusively, it may not even have JVMs installed on any of its production servers.
Earlier quoted context omitted.
The "NASCAR slide" can also appeal to emotions, as a form of peer pressure. "Oh I wanna be like the big guys, and the big guys use this, I should do what they do".
In the enterprise world this is done via user groups - http://www.sap.com/communities/user-groups.html You'd be surprised how often competitors (let's say BP and Shell for example) make purchasing decision after discussions at user group events, simply "to keep up with the Jones's".