The common theme in this article seems to be about planning approaches to and implementing algorithms. I think there's more to being a successful employed prog

The common theme in this article seems to be about planning approaches to and implementing algorithms. I think there's more to being a successful employed programmer than that. How do you avoid people who are nice as pie in the interview, but play politics and are rude to people under your nose on the job? How do you avoid people who can deploy algorithms on demand, but have very little motivation day to day and fail to get anything substantial done? At a job, you're interacting with people every day. I don't think you're looking for the best-performing algorithm every day. In most cases, best performance doesn't matter.