Joel on Software

• Stack Overflow Podcast #32
• 

  This week Jeff and I talk about software piracy, some performance improvements on the site, dealing with criticism, great programmer’s offices, and more, in Stack Overflow Podcast #32.

  Not loving your job? Visit the Joel on Software Job Board: Great software jobs, great people.

  ]]>
• My Style of Servant Leadership
• 

  “As for the sergeant major’s job, it basically consisted of two main duties: being the chief disciplinary officer and maintaining the physical infrastructure of the base. As such, he was a terror to everyone in the battalion. Most people knew him only from the way he strutted around, conducting inspections, screaming at the top of his lungs, and demanding impossibly high standards of order and cleanliness in what was essentially a bunch of tents in the middle of the desert—tents that were alternately dust-choked or mud-choked, depending on the rain situation.”

  From my latest Inc. column: My Style of Servant Leadership

  Not loving your job? Visit the Joel on Software Job Board: Great software jobs, great people.

  ]]>
• Stack Overflow Podcast #31
• 

  In the Thanksgiving edition of the Stack Overflow podcast, episode 31, Jeff and I discuss math, status reports, the economic downturn, the business case for nice office space, SQL parameters, programming “slumps,” and a whole lot more.

  Not loving your job? Visit the Joel on Software Job Board: Great software jobs, great people.

  ]]>
• Exploding Offer Season
• 

  If you’re a college student applying for jobs or summer internships, you’re at something of a disadvantage when it comes to negotiation. That’s because the recruiter does these negotiations for a living, while you’re probably doing it for the first time.

  I want to warn you about one trick that’s very common with on-campus recruiters: the cynical “exploding offer.”

  Here’s what happens. You get invited to interview at a good company. There’s an on-campus interview; maybe you even fly off to the company HQ for another round of interviews and cocktails. You ace the interview, of course. They make you an offer.

  “That sounds great,” you say.

  “So, when can you let us know?”

  “Well,” you tell them, “I have another interview coming up in January. So I’ll let you know right after that.”

  “Oh,” they say. “That might be a problem. We really have to know by December 31st. Can you let us know by December 31st?”

  Tada! The magnificent “exploding offer.”

  Here’s what you’re thinking. You’re thinking, well, that’s a good company, not my first choice, but still a good offer, and I’d hate to lose this opportunity. And you don’t know for sure if your number one choice would even hire you. So you accept the offer at your second-choice company and never go to any other interviews.

  And now, you lost out. You’re going to spend several years of your life in some cold dark cubicle with a crazy boss who couldn’t program a twenty out of an ATM, while some recruiter somewhere gets a $1000 bonus because she was better at negotiating than you were.

  Career counselors know this, and almost universally prohibit it. Every campus recruiting center has rules requiring every company that recruits on campus to give students a reasonable amount of time to make a decision and consider other offers.

  The trouble is, the recruiters at the second-rate companies don’t give a shit. They know that you’re a college kid and you don’t want to mess things up with your first real job and you’re not going to call them on it. They know that they’re a second-rate company: good enough, but nobody’s dream job, and they know that they can’t get first-rate students unless they use pressure tactics like exploding offers.

  And the worst thing that career centers can do is kick them off campus. Big whoop. So they hold their recruiting sessions and interviews in a hotel next to the campus instead of at the career center.

  Here’s your strategy, as a student, to make sure you get the job you want.

  1. Schedule your interviews as close together as possible.

  2. If you get an exploding offer from a company that’s not your first choice, push back. Say, “I’m sorry, I’m not going to be able to give you an answer until January 14th. I hope that’s OK.” Almost any company, when pressed, will give you a chance to compare offers. Don’t worry about burning bridges or pissing anyone off. Trust me on this one: there’s not a single hiring manager in the world who wants to hire you but would get mad just because you’re considering other offers. It actually works the other way. When they realize you’re in demand, they’ll want you more.

  3. In the rare case that they don’t accept that, accept the exploding offer at the last minute, but go to the other interviews anyway. Don’t cash any signing bonus checks, don’t sign anything, just accept the offer verbally. If you get a better offer later, call back the slimy company and tell them you changed your mind. Look, Microsoft hires thousands of college kids every year. If one of them doesn’t show up I think they’ll survive. Anyway, since we instituted that 13th amendment thing, they can’t force you to work for them.

  If you do find yourself forced to renege on an offer, be classy about it. Don’t do this unless you are absolutely forced to because they literally refused to give you a chance to hear from your first choice company. And let them know right away you’re not going to take the offer, so they have a chance to fill the position with someone else.

  Campus recruiters count on student’s high ethical standards. Almost all students think, “gosh, I promised I’ll go work for them, and I’m going to keep my promise.” And that’s great, that’s a commendable attitude. Definitely. But unethical recruiters that don’t care about your future and don’t want you to compare different companies are going to take advantage of your ethics so they can get their bonus. And that’s just not fair.

  Not loving your job? Visit the Joel on Software Job Board: Great software jobs, great people.

  ]]>
• Stack Overflow Podcast #30
• 

  Stack Overflow Podcast episode 30 is up, with special guest Richard White of UserVoice.

  Not loving your job? Visit the Joel on Software Job Board: Great software jobs, great people.

  ]]>
• Anecdotes
• 

  Michiko Kakutani reviews Malcolm Gladwell's latest book in the New York Times: “Much of what Mr. Gladwell has to say about superstars is little more than common sense: that talent alone is not enough to ensure success, that opportunity, hard work, timing and luck play important roles as well. The problem is that he then tries to extrapolate these observations into broader hypotheses about success. These hypotheses not only rely heavily on suggestion and innuendo, but they also pivot deceptively around various anecdotes and studies that are selective in the extreme: the reader has no idea how representative such examples are, or how reliable — or dated — any particular study might be.”

  This review captures what's been driving me crazy over the last year... an unbelievable proliferation of anecdotes disguised as science, self-professed experts writing about things they actually know nothing about, and amusing stories disguised as metaphors for how the world works. Whether it's Thomas Friedman, who, it seems, cannot go a whole week without inventing a new fruit-based metaphor explaining everything about the entire modern world, all based on some random jibberish he misunderstood from a taxi driver in Kuala Lumpur, or Malcolm Gladwell with his weak theories on tipping points, crazy incorrect theories on first impressions, or utterly lunatic theories on experts, it all becomes insanely popular simply because the stories are fun and interesting and everybody wants to hear a good story. Spare me.

  Friedman and Gladwell's outsized, flat-world success has lead to a huge number of wannabes. I was really looking forward to reading Simplexity, because it sounded like an interesting topic, until I settled down with it tonight and discovered that it was chock-full of all those amusing bedtime stories about the map of the cholera plague in London in 1854, which I've heard a million times, and then suddenly I noticed (shock!) that not only was the author a journalist, not a scientist, but he was actually an editor at Time Magazine, which has an editorial method in which editors write stories based on notes submitted by reporters (the reporters don't write their own stories), so it's practically designed to get everything wrong, to insure that, no matter how ignorant the reporters are on an issue, they'll find someone who knows even less to write the actual story. Panicking, I began to flip through the book at random. There's that story about Don Norman and complicated user interfaces. Here he is reading Nassim Taleb. I've heard all these anecdotes! Stop, already! I threw the book away in frustration.

  This is the third one of the day. My business partner Jeff Atwood was busy extracting himself from the flamewars he started by writing an article on, of all things, NP-completeness, which is, actually, something that it's possible to know something about, because it's not a vague sociological hypotheticoncept like simplexiflatness or blinkoutliers, it's actually a real, important result from Computer Science, with a rigorous definition and lots of published papers, and poor Jeff got himself in something of a pickle by writing a book review when he hadn't read the book, and fortunately, he has comments on his blog, so his readers called him out on it.

  Now, I am not one to throw stones. Heck, I practically invented the formula of "tell a funny story and then get all serious and show how this is amusing anecdote just goes to show that (one thing|the other) is a universal truth." And everybody is like, oh yes! how true! and they link to it with approval, and it zooms to the top of Slashdot. And six years later, a new king arises who did not know Joel, and he writes up another amusing anecdote, really, it's the same anecdote, and he uses it to prove the exact opposite, and everyone is like, oh yes! how true! and it zooms to the top of Reddit.

  This is not the way to move science forward. On Sunday Dave Winer [partially] defined "great blogging" as "people talking about things they know about, not just expressing opinions about things they are not experts in (nothing wrong with that, of course)." Can we get some more of that, please? Thanks.

  Not loving your job? Visit the Joel on Software Job Board: Great software jobs, great people.

  ]]>
• Stack Overflow Podcast #29
• 

  

  In this week's Stack Overflow podcast, Jeff and I talk about video games, programming languages that aren't "in" English, and hiring great programmers.

  Not loving your job? Visit the Joel on Software Job Board: Great software jobs, great people.

  ]]>