 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Interview preparation</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/interview-preparation/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/interview-preparation/</link>
	<description></description>
	<lastBuildDate>Mon, 20 May 2013 18:21:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: meandyou</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/interview-preparation/#comment-81421</link>
		<dc:creator>meandyou</dc:creator>
		<pubDate>Mon, 13 Sep 2010 14:22:19 +0000</pubDate>
		<guid isPermaLink="false">#comment-81421</guid>
		<description><![CDATA[Even tho I agree that programming ET. AL. is like riding a bike (that is to say that anyone with 30+ years experience knows a lot), unfortunately too many pointy haired bosses only want to hear the latest buzz words.  
 
I agree with you that your old skills should still suffice.  What you will find is that almost no one does the analysis much any more - they just start coding.  The requirements gathering, the functional analysis phase, the business rules definitions ... I think a LOT of places just skip past that.    And that is a shame.  (might that be one reason that new systems don&#039;t last for 20 or 30 years anymore?)

As team leader, perhaps your skills to motivate and lead and bring the group together  will out weigh your lack of &quot;new&quot; skills (which are the old ones just repackaged).  Perhaps you could focus on the big projects you have worked on; numbers of people, complexity, size, etc to show you will not get lost in this project. 

How this turns out for you may well hinge on who it is that is conducting the interview (and what their attitude).]]></description>
		<content:encoded><![CDATA[<p>Even tho I agree that programming ET. AL. is like riding a bike (that is to say that anyone with 30+ years experience knows a lot), unfortunately too many pointy haired bosses only want to hear the latest buzz words.  </p>
<p>I agree with you that your old skills should still suffice.  What you will find is that almost no one does the analysis much any more &#8211; they just start coding.  The requirements gathering, the functional analysis phase, the business rules definitions &#8230; I think a LOT of places just skip past that.    And that is a shame.  (might that be one reason that new systems don&#8217;t last for 20 or 30 years anymore?)</p>
<p>As team leader, perhaps your skills to motivate and lead and bring the group together  will out weigh your lack of &#8220;new&#8221; skills (which are the old ones just repackaged).  Perhaps you could focus on the big projects you have worked on; numbers of people, complexity, size, etc to show you will not get lost in this project. </p>
<p>How this turns out for you may well hinge on who it is that is conducting the interview (and what their attitude).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 6/9 queries in 0.021 seconds using memcached
Object Caching 268/271 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-20 19:14:19 -->