http://blogs.msdn.com/b/steverowe/archive/2008/08/07/the-company-you-work-for-matters.aspxIn an episode of Stack Overflow Podcast, Jeff Atwood made an interesting point.&#160; He spoke of the difference between companies that deliver code as their product (like Microsoft) and companies who use code to support other business interests (theen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/steverowe/archive/2008/08/07/the-company-you-work-for-matters.aspx#8939084Wed, 10 Sep 2008 08:37:45 GMT91d46819-8472-40ad-a661-2c78acb4018c:8939084em vee<p>It's bad all over.</p> <p>I've worked for both types of companies, including several well known brand name software companies.</p> <p>The pressure to 'ship' undercuts quality. Always. Most managers don't know what good code is or good development practice, all they know is how to look at a calendar.</p> <p>Frankly, having worked at both, I prefer companies who have a material business, which needs to be supported by IT/programming. Yes, the managers are just as clueless, and nobody cares about how well crafted your code is, but at least your efforts relate to something real.</p> <p>Btw, being 'asked to give more of yourself' sounds a lot like a euphemism for mandatory unpaid overtime.</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=8939084" width="1" height="1">http://blogs.msdn.com/b/steverowe/archive/2008/08/07/the-company-you-work-for-matters.aspx#8919789Tue, 02 Sep 2008 14:08:11 GMT91d46819-8472-40ad-a661-2c78acb4018c:8919789Dale<p>&quot;If you love to code, you really don't want to work in an IT department.&quot;</p> <p>And that sums it up. &nbsp;When you work for an IT department, it's a &quot;get it done&quot; mentality. &nbsp;There's little beauty in the code you cut :-(</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=8919789" width="1" height="1">