3 ms·
Thank you for sharing your experience! New languages is one of the "fun" parts of programming. Except at work. There are legitimate problems of legibility, mai
by gandreani 8y ago
Thank you for sharing your experience! New languages is one of the "fun" parts of programming. Except at work.
There are legitimate problems of legibility, maintainability, and training when introducing new stuff into the stack. Then there's the balance that we have to strike with re-writing old with new. How much do we gain with the new vs how much time is it gonna cost?
Lately, these have been the things I worry about instead of algorithm design or product design. Precisely the things we don't get taught in school or get interviewed for
- brightball 8y agoTrue. In my experience that largely depends on the environment. In Java or .NET shops, there is a significant investment in the surrounding infrastructure where the code is deployed. Has a huge impact in cost of switching. That's before even factoring in some of the inside baseball related to "discounts" on products like SQL Server if you have a certain number of employees with Microsoft certs. For just about everything else though...it's not nearly as much of a headache.
- deleted 8y ago[deleted]
- gandreani 8y agoOh man. Those discounts sounds like such a headache. It's hard enough considering the asks for one department already... Environment is definitely the key. We don't use either of those languages but we do run our site on a dozen or so servers. There's a fair bit of coupling that can eventually add up when you run the same apps on the same servers for years