<?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: Making a Great Place for Developers to Work</title>
	<atom:link href="http://www.brightmix.com/blog/making-a-great-place-for-developers-to-work/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.brightmix.com/blog/making-a-great-place-for-developers-to-work/</link>
	<description></description>
	<lastBuildDate>Tue, 02 Mar 2010 13:21:54 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: BrightMix 2008 Summer Internship Program! &#124; BrightMix</title>
		<link>http://www.brightmix.com/blog/making-a-great-place-for-developers-to-work/comment-page-1/#comment-590</link>
		<dc:creator>BrightMix 2008 Summer Internship Program! &#124; BrightMix</dc:creator>
		<pubDate>Mon, 12 Jan 2009 05:53:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.brightmix.com//2008/02/07/making-a-great-place-for-developers-to-work#comment-590</guid>
		<description>[...] Oh, and Having Fun at Work [...]</description>
		<content:encoded><![CDATA[<p>[...] Oh, and Having Fun at Work [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://www.brightmix.com/blog/making-a-great-place-for-developers-to-work/comment-page-1/#comment-82</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Thu, 20 Dec 2007 03:14:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.brightmix.com//2008/02/07/making-a-great-place-for-developers-to-work#comment-82</guid>
		<description>Dusty, I couldn&#039;t agree more.  I happen to be fortunate enough to finally work in an environment similar to the one you describe, and I can&#039;t tell you how nice it is.

I actually like my job... I&#039;ve always liked programming, but never like who I&#039;ve programmed for... until now!

I think the other important thing to mention here is that when you create an environment like this, and run your organization as such, it is also important to not adopt a &quot;too cool for the room&quot; attitude.  I turned down a great opportunity for a company that touted all these fun benefits, but they turned out to be a bunch of cocky jerks that thought I should feel privileged to work in their presence.  Just &#039;cause you have a Wii and a cool loft-style open office, doesn&#039;t mean that you&#039;ve got it down.  The attitude of the management is equally important, and it sounds like you guys have the right one.

Keep it up!</description>
		<content:encoded><![CDATA[<p>Dusty, I couldn&#8217;t agree more.  I happen to be fortunate enough to finally work in an environment similar to the one you describe, and I can&#8217;t tell you how nice it is.</p>
<p>I actually like my job&#8230; I&#8217;ve always liked programming, but never like who I&#8217;ve programmed for&#8230; until now!</p>
<p>I think the other important thing to mention here is that when you create an environment like this, and run your organization as such, it is also important to not adopt a &quot;too cool for the room&quot; attitude.  I turned down a great opportunity for a company that touted all these fun benefits, but they turned out to be a bunch of cocky jerks that thought I should feel privileged to work in their presence.  Just &#8217;cause you have a Wii and a cool loft-style open office, doesn&#8217;t mean that you&#8217;ve got it down.  The attitude of the management is equally important, and it sounds like you guys have the right one.</p>
<p>Keep it up!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Holden</title>
		<link>http://www.brightmix.com/blog/making-a-great-place-for-developers-to-work/comment-page-1/#comment-83</link>
		<dc:creator>Holden</dc:creator>
		<pubDate>Thu, 20 Dec 2007 03:14:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.brightmix.com//2008/02/07/making-a-great-place-for-developers-to-work#comment-83</guid>
		<description>This environment is ideal for most developers assuming Brightmix doesn&#039;t fall into the &quot;elitist developers sipping cappuccino and walking on hardwood floors&quot; pit where it&#039;s decided on day one whether you will be liked or not based on your wardrobe, haircut, iPod playlist, and requirement that you be under age 30.

e.g. Ikea Web Development, a neo-beatnik company.

Hiring your first developer is a critical time.  This is where the tone of company culture at Brightmix will be set for all time.  It&#039;s easy at this point to hire someone that&#039;s a friend, who will in turn recommend a friend when you bring on your fourth, and so on and so forth.  Then next thing you know the office is one big click.  Then  comes along the one guy who wasn&#039;t hired off of employee referral who walks into work, realizes it&#039;s a good ole boy club, and hates it.  Or worse, you have to let someone go and their half dozen friends quit with them and you lose your entire development staff.

As you employ more people and take on more work, more of your time will be spent running the company and handling the clients than writing code.  In a three person company, everyone codes.  In 15 person company, someone has to process payroll, do annual reviews, administer benefits, deal with a much larger client list, resolve problems between conflicting team members, remember to order flowers because Bob&#039;s grandfather passed away, deal with the neighbors because your employees are taking up more than their fair share of the parking lot, provide evidence when a former employee files for unemployment, handle accounts payable and receivable, send bad clients to collections, deal with that new client in the financial industry that wants to know if your employees have all had criminal background checks and drug screenings, etc..

It&#039;s a real pain when you&#039;re so big that you can&#039;t accomplish those things in just one afternoon and too small to cost-effectively hire non-technical support staff to do them for you.

At that point, who the bosses are becomes less important to the employees as who their co-workers are.  Why?  They&#039;re working less and less directly with you and more and more directly with their peers.  Is that 40 year old developer that brings much needed experience, maturity, and industry contacts to the table going to get along with the 21 year old developer that just can&#039;t get over the fact that his co-worker is 40?

Basically, you need someone that is going to fit into a homogenous group of 3 developers but in a few years will also fit into a diverse group of many more developers.  Additionally, at your current size they&#039;re going to need to fill many roles.  They have to be developers that don&#039;t mind talking to clients, putting on their business hat, or changing light bulbs.</description>
		<content:encoded><![CDATA[<p>This environment is ideal for most developers assuming Brightmix doesn&#8217;t fall into the &quot;elitist developers sipping cappuccino and walking on hardwood floors&quot; pit where it&#8217;s decided on day one whether you will be liked or not based on your wardrobe, haircut, iPod playlist, and requirement that you be under age 30.</p>
<p>e.g. Ikea Web Development, a neo-beatnik company.</p>
<p>Hiring your first developer is a critical time.  This is where the tone of company culture at Brightmix will be set for all time.  It&#8217;s easy at this point to hire someone that&#8217;s a friend, who will in turn recommend a friend when you bring on your fourth, and so on and so forth.  Then next thing you know the office is one big click.  Then  comes along the one guy who wasn&#8217;t hired off of employee referral who walks into work, realizes it&#8217;s a good ole boy club, and hates it.  Or worse, you have to let someone go and their half dozen friends quit with them and you lose your entire development staff.</p>
<p>As you employ more people and take on more work, more of your time will be spent running the company and handling the clients than writing code.  In a three person company, everyone codes.  In 15 person company, someone has to process payroll, do annual reviews, administer benefits, deal with a much larger client list, resolve problems between conflicting team members, remember to order flowers because Bob&#8217;s grandfather passed away, deal with the neighbors because your employees are taking up more than their fair share of the parking lot, provide evidence when a former employee files for unemployment, handle accounts payable and receivable, send bad clients to collections, deal with that new client in the financial industry that wants to know if your employees have all had criminal background checks and drug screenings, etc..</p>
<p>It&#8217;s a real pain when you&#8217;re so big that you can&#8217;t accomplish those things in just one afternoon and too small to cost-effectively hire non-technical support staff to do them for you.</p>
<p>At that point, who the bosses are becomes less important to the employees as who their co-workers are.  Why?  They&#8217;re working less and less directly with you and more and more directly with their peers.  Is that 40 year old developer that brings much needed experience, maturity, and industry contacts to the table going to get along with the 21 year old developer that just can&#8217;t get over the fact that his co-worker is 40?</p>
<p>Basically, you need someone that is going to fit into a homogenous group of 3 developers but in a few years will also fit into a diverse group of many more developers.  Additionally, at your current size they&#8217;re going to need to fill many roles.  They have to be developers that don&#8217;t mind talking to clients, putting on their business hat, or changing light bulbs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
