<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>GeekMBA360: Beat Recession. Grow Career. Build Wealth. - Latest Comments in Don&amp;#8217;t work for the same company for too long</title><link>http://geekmba360.disqus.com/</link><description></description><atom:link href="http://geekmba360.disqus.com/don8217t_work_for_the_same_company_for_too_long/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Sat, 13 Feb 2010 18:59:14 -0000</lastBuildDate><item><title>Re: Don&amp;#8217;t work for the same company for too long</title><link>http://www.GeekMBA360.com/dont-work-for-the-same-company-for-too-long#comment-34139299</link><description>&lt;p&gt;Very true, especially for the IT industry, and I couldn't agree with you more on your advice. This is especially try for many bank IT staff which keep working with long outdated mainframe systems with little to no chance for getting a new job outside their own firm or industry. Some specific examples: I hear that Bloomberg has a lot of proprietary tools and languages that effectively renders most of their IT employees outdated and unable to switch jobs easily. The medical informatics firm Epic Systems is also similar, with a large number of its IT employees using a specialized and outdated CACHE programming language which very few other companies use. On second thought...could this be a ploy by these companies to hang onto their staff for a long time ?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fjxx</dc:creator><pubDate>Sat, 13 Feb 2010 18:59:14 -0000</pubDate></item></channel></rss>
