Multi-threaded developer


Once upon a time a kick-ass developer I knew told me that a good developer needs to be multi-threaded and run the following threads

  1. The main worker thread: This is the one used to code up 3-tier applications for your employer. This pays for the rent and for that fancy big car.
  2. The core thread: This is the one that's used to read up data-structures, OS and other fundamental CS stuff which helps you to join into discussion when folks are discussing threaded BST. This also helps you to crack an interview in case you need a new job.
  3. The cool thread: This is the one you use to read up about Silver Light Mobile, ASP.NET MVC Framework, JSON, etc. This keeps you up to date and let's you hang around with other geeks like Scot Hanselman and Don Box

The same person also told me that real programmers do not blog, he asked me "Do you know about Dave Cutler or Linus Torvald's blog?". So I guess we can safely ignore him 🙂

Comments (1)

  1. R says:

    Interesting point of view, and this reminds me of one of the frustrating things about this field:  If the "core thread" is something that we have to REMIND ourselves to stay up on, to prepare for the very rare case in which we have to use some algorithm from our undergrad days, then why is it needed for job interviews too?  If it’s not knowledge that one needs every day, or even every year, then why do interviewers look for it?

    I was surprised the last time I looked for a job to be asked about stuff I hadn’t learned since my freshman year of college.  Years ago I could have told you the difference between a depth-first and breadth-first search, and I know that it’s basic CS stuff, but I just hadn’t thought about it for years since then, despite the 7 years of university study and industry programming work since then.

    It’s embarassing to get stuck in an interview on stuff like this, but on the other hand is it really vitally important to a programmer to have that knowledge on hand at all times?  I passed the class in college in which I learned it when I was 18, and google can remind me of the answer in a few seconds, and I’ve managed to be a gainfully-employed programmer for years without knowing it, so isn’t it a bit silly to say that someone needs to know it for an interview?

Skip to main content