Sundries

by Krishna on April 13, 2009

sundries

Or, translated from Australian, miscellaneous items, in this case, too small to write a long blog post on. And a bit too long for Twittering.  So here are a few of those thoughts:

  1. Most newspapers have fact checkers for their articles and reports. Newspapers are dying and being replaced by bloggers and other websites. Several bloggers today have subscribes that surpass the circulation of small newspapers. How much fact checking are they doing? And how many errors are they fixing? Considering that most bloggers are preaching to the converted, that is not happening anytime soon. So the lesson is “reader beware”.
  2. On that note, there is a meme that technology bloggers should worry about what they write, because they could be a bad influence on inexperienced programmers. I don’t agree because the person who doesn’t do more research on both sides of any topic will always get into trouble, regardless of the experience level. And paternalism is never a good teaching strategy.
  3. Programming is like a game you want to learn, like, say, tennis. You don’t learn it by reading all the book on strategies and tactics. You go out and play (code). And then, when you read the books, it makes it much clearer how you can use those tactics better. It doesn’t mean that the books are wrong or useless. It just means that they are more valuable when you have already practiced some.
  4. The saddest person is the bad programmer who genuinely wants to improve, but has no passion for his job. He doesn’t understand that you cannot be a better programmer by simply taking shortcuts. You have to possess some intrinsic traits such as being curious about new things and being excited about solving problems. If you don’t, programming is probably not the right profession.
  5. People like talking about the 10x programmer – the one who is 10 times more productive than your average programmer. That’s great, but we should also talk about the 0.1x programmer who is dragging down the rest of the team. It is not even about the speed at which tasks get accomplished. It is whether they even get completed or, worst case scenario, started. The 0.1x programmer is not the actual worst programmer (because they get fired), but the person who just does enough NOT to be sacked.

[Photo licensed from CarbonNYC]

Comments on this entry are closed.

Previous post:

Next post: