3 ms·
I get where that is going, and agree with the sentiment. But this assumes that companies, engineering teams and problem domains all perfectly overlap. I'm a sy
by _jal 7y ago
I get where that is going, and agree with the sentiment. But this assumes that companies, engineering teams and problem domains all perfectly overlap.
I'm a systems guy in a Java shop. Ignoring obvious nonstarters like trying to shove Java into early Linux boot, this still implies I should be hiring Java programmers for systems engineers. Which, no, not only don't I care, doing that would select for a very small subset of available candidates.
A nice thought experiment, but not practical.
- rho4 7y agoI would try to use Java to manage / generate necessary Linux boot scripts. Use Java to manage Linux servers etc.
- _jal 7y agoFeel free. We won't. There are multiple reasons, but the big one is there is almost no overlap between the engineering team's reason for existing (writing and maintaining line-of-business applications) and ours (keep systems up, compliant, performant and safe). But if it makes you happier, one tool we use is Puppet. That runs in JRuby in a JVM to execute their own weird DSL. So to use it in a nontrivial environment, you need to be able to tune Java and write both Ruby and Puppetese.