note
cjf
<p>Ah, Mr. Spolsky, I don't think I'll ever understand why so many people link to his articles. Quoth the Joel:</p>
<blockquote><i>Get better people into the team. Get involved in hiring and interviewing, and recruit good candidates to join the team.</i></blockquote>
<p>Okay, if you're involved in hiring people, you probably aren't a grunt. If your grunts are doing your hiring, your company has major problems.</p>
<blockquote><i>At some point, one of these geniuses will spend two weeks writing a bit of code that is so unbelievably bad that it can never work. You're tempted to spend the fifteen minutes that it takes to rewrite the thing correctly from scratch. Resist the temptation. You've got a perfect opportunity to neutralize this moron for several months. Just keep reporting bugs against their code. They will have no choice but to keep slogging away at it for months until you can't find any more bugs.</i></blockquote>
<p>Does that seem like a bad idea to anyone else? It wouldn't exactly create a good team environment would it? If somebody's code sucks, help them improve it. This can easily be done in a non-threatening way. Don't forget to look at their side of the issue as well, who knows, you might be the "Bozo" programmer.</p>
<blockquote><i>Look for ways to get out of this environment. Take a laptop to the company cafeteria, where there are lots of tables that are empty most of the day (and nobody can find you). Book a conference room for the whole day and write code there</i></blockquote>
<p>Okay, so if you're new to a company make it very difficult for anyone to find you? Again, great way to build a good environment and get people to listen to you. Not to mention wasting valuable conference room time that could be needed for useless meetings.</p>
<p>Mind you, his first point wasn't so bad <i>"Just Do It"</i> but I guess Nike wouldn't like it if that was his entire article. Too bad, it would have been far better advice.</p>
177032
177322