4 ms·
If you spent your life becoming very efficient in a particular environment, there's an incentive to keep this environment from changing, and not to expend any e
by nine_k 8y ago
If you spent your life becoming very efficient in a particular environment, there's an incentive to keep this environment from changing, and not to expend any effort to learn a new environment. That learning capacity can be more efficiently spent elsewhere.
(An IT illustration: there are still places running RHEL6 in production and not seeing an effort to migrate from it worth the while. They have more important things to do.)
- hinkley 8y agoA big component of mastery is wiring your brain to make the right decision without sweating over the details like you did when you were 25. Replacing problem solving with intuition. But what happens 20 years later when your intuition is no longer correct? Or when someone keeps asking why? You’re out of practice, And you’re trying to rewire a part of your brain that is no longer part of your internal dialog. Teaching seems to be one way to avoid this. You have to keep defending your decisions. Switching specializations (or creating new ones) is another. The only other way I know is to seek outside help, and that level of humility is rare in experts.
- mycall 8y agoThere is another way. Keep challenging yourself with new projects, be a life learner.
- deleted 8y ago[deleted]
- cbcoutinho 8y agoWhen all you have is a hammer, everything looks like a nail
- mmirate 8y agoIt gets better: there are places selling their software via hardware appliances that run RHEL6.
- mikec3010 8y agoThat is better, actually. If it's proven for that many years why mess with it? Why assume that older is unilaterally worse?
- mmirate 8y agoEcliptic Curve cryptography. In-tree driver modules for last year's 10Gb Ethernet cards. Python 2.7, let alone 3. Official support for kernel 4.x. I've barely been in the industry for 90 days and I've already had to deal with the lack of the above in RHEL6. (Indirectly, mind you; but I believe that the transition between RHEL6 and CentOS6 is negligible for the current topic.)
- mikec3010 8y agoHypothetically, if you needed python couldn't you either compile it to binary or just install the runtime ? I don't see how a language would be coupled to the version of Linux.
- mmirate 8y agoDoing so means putting all Python packages into a single opaque OS-level package. Not fun when your build system and related infrastructure, were all designed to work with OS-level packages.
- icebraining 8y agoWhy? You just use package dependencies to indicated that they depend on the New Python.
- mmirate 8y agoThird-party dependencies. Their BRPMs will all install to the OS's old Python. Pull them from PyPI using setup.py, and we get the problem I describe; the alternative is to build our own BRPMs, which is a massive headache to set up.
- soperj 8y ago>there are still places running RHEL6 in production We just got off of RHEL5, so I can understand why there are people still running 6.
- jethro_tell 8y agoThere are places that just forked RHEL5ish and update the kernel and packages. At some point it's a mess, but until then, just keep patching.
- mmt 8y ago> An IT illustration: there are still places running RHEL6 in production and not seeing an effort to migrate from it worth the while. I recently interviewed at a startup (though a reasonably far-along/mature, if not spectacularly successful by VC standards) that was both running RHEL6 and depending a remarkable amount on "enterprise" gear, software, and support, which seemed incongruous for any small company, let alone a startup. They did see it as worthwhile to "migrate" to CentOS6, but I'm pretty sure the interviewer who was the incumbent rejected me quickly and strenuously after I admitted a preference for Ubuntu (due to its package ecosystem better catering to a wider array of developers, making my DevOps culture evangelism and implementation that much easier) and a focus on frugality first when it comes to hardware (that being a huge benefit of it being a commodity). > They have more important things to do. Poe's Law aside, I do actually find this to be a valid argument, if it's presented eyes-open, rather than just through inertia. That is, there's a difference between having considered the migration and deciding it's not worth it (or that the "more important things" are more worth it and take priority) and not having considered the migration at all because those "more important things" completely consumed everyone's attention. I don't mean to present these as a false dichotomy, just two extremes that illustrate my point.
- flukus 8y ago> (An IT illustration: there are still places running RHEL6 in production and not seeing an effort to migrate from it worth the while. They have more important things to do.) We're currently re-building all our systems to target RHEL6 because that's what the execs decided, if we're lucky the project will be done before it's end of lifed. They also decided that we'd be using modern c++, more modern than the GCC that ships with RHEL6. Thanks to these largely incompatible requirements the team responsible has practically built their own distro on top of RHEL6, with a newer gcc and a rebuild of all the libraries we use complete with it's own package management system. I think it's customized enough that a highly doubt redhat could off us any support anyway.