Company vs. Developer Needs

There is a fundamental schism between the needs of a software developer and the needs of a business around technology trends.  Most developers I have met want to stay current with new technologies.  Companies need to keep software platforms stable and making money to keep the lights on.  These two concepts would appear to be against each other.  In practice this often the case.

For example, a project I previously worked on leveraged knockout heavily.  The business doesn't care about knockout in the slightest, but the concepts in the product are key to the business success.  This product is actively being worked on, while knockout works for it, how can the company expect to keep developers when they can't pursue new technologies and ideas professionally?

I'm cautious about what I put on my resume.  If i have not done something professionally it doesn't go on my resume.  Yes, I have played with nodejs, but only from a hobbyist perspective.  Companies expect that developers can learn new technologies on their own time, or as part of a continuing education policy.  This is only half the equation.  Companies also need to let developers put new technologies into action.  This will help developers stay marketable, and if developers remain marketable they may be willing to stay longer.

Developers need to always be cognizant of the needs of the business.  That shiny paycheck that we get must come from somewhere.  Every new technology can't be used to re-implement feature set after feature set.  There is a time and place to look into new features being implemented with new technologies that won't significantly interfere with cash flow.

This schism between company and software developer almost always ensures that your top talent will move on to other pastures, either within or outside your company.  This is not necessarily bad.  Especially if the product is in a revenue generating state where a small team can swap in and out of the project for maintenance needs.

Companies, such as Google, have adopted a scenario where some idea can be pursued independently of other business needs.  I think that is great if you have an awesome revenue stream and ubiquitous service.

Overall I think that companies need to keep an eye on development trends.  It's a good idea to have a technology review board for major products that takes advice from teams and produces action items for how to progress with proper, timely integration.  Overall I think that developers tend to have a myopic viewpoint as to their role in keeping up with business needs.  Keeping other viewpoints in line won't solve the problem, but may help put band-aids in place for the benefit of everyone.