recent blog posts related to software careers, and career advice

Broncos hiring more coaches (to teach technique)

The Denver Post has an article about how the Broncos are (finally) hiring more coaches, hopefully to teach “technique” to their players. They’ve been horrible at developing players under the Elway regime, and hopefully this is a positive sign.

When I owned my software company I learned how important training was. At first we hired people who were generally experts at what they did, but as we tried to expand we realized that not everyone was an expert, or, if they were an expert at web development using Framework A, they weren’t an expert at Java Swing development, or vice-versa. I’m not saying we always did a good job at training (in large part because some of the initial hires didn’t think it was necessary), but over time we learned and tried.

A recommendation for would-be book writers

If you’ve read any of my books (like the Scala Cookbook or Functional Programming, Simplified), and thought, “Hey, I can write a book,” I encourage you to do so. One book that has been helpful in my writing career is William Zinsser’s On Writing Well: The Classic Guide to Writing Nonfiction. If you’re seriously thinking about writing a book about programming or any other technical topic, it’s a good read.

People don’t respect your time as an at-home writer

One thing I learned about being a full-time, at-home writer: people don’t respect your time. It’s like, “You’re a writer? Haha, that’s funny. Why don’t you come over and help me paint my house? I’m counting on you.” That sort of thing.

The time a recruiter told me to “play dumb”

I was just reminded of the time a recruiter told me to “play dumb” when a particular person interviewed me, because that person didn’t like to be challenged, and had to feel like he was the smartest person in the room. I couldn’t bring myself to do that; I figured if that was the way it was going to be, I didn’t want to work there.