We’ve decided to integrate the blog with the rest of the Making it Big Careers site.  You can now follow this blog at:

The old blog site, will no longer be used for new posts. Most of the old posts have been migrated to the new location.

If you are a subscriber, please take 10 seconds to subscribe to the new blog feed.

Our apologies for any inconvenience this causes. 

To our readers and subscribers – THANK YOU!


Sam Lightstone


Why popular programming languages may be bad for your programming career

A careful reading of Making it Big in Software will surface two curious observations. First,  I studied the popularity of different programming languages and platforms.  Not surprisingly  I found the Java is the most popular programming language in the world.  Nice, but not exactly world news.  It stands to reason that if Java is the most widely used, it’s where the job are,  right?  So if you wan to be marketable, you may draw the conclusion that you need to stay fresh on your Java skills.   Then I interviewed Mark Russinovich, Microsoft Technical Fellow, and Windows architect. I asked Mark for his thoughts on what people should keep in mind in order to have successful careers in software. Here’s part of the advice he offered:

“Try to differentiate yourself. For example, when Java exploded in the mid-1990s, everybody became a Java programmer, and the market became flooded with cookie-cutter Java programmers. It’s really hard for people to stand out as something that isn’t easily replaceable in that world. My whole career I have tried to stay away from that. Operating system internals, while not considered particularly sexy or part of the mainstream, have allowed me to stand out because of the relatively few people who go into that and the perception “Wow, that’s really hard.” Stay away from the mainstream and the crowds, and find something that is gonna be stable—not just flash-in-the-pan technology.”

Mark isn’t saying you shouldn’t be a good Java programmer, and neither am I.   Knowing Java is definitely good! But if that’s you primary skill and claim to fame it’s going to be hard to distinguish yourself.   Be distinguishable. Most of the time programming skills are to software as hammer, lathe and drill are to a carpenter. Tools of the trade, yes, bu not where the deeper talent lies. Being an expert in tools doesn’t make you a great carpenter, because the essence is knowing how to make the table, the cabinet, or the armoire.  In most cases software is the same way, and programming simply provides the tool to apply your real talent. What really distinguished you is your deeper knowledge of the domain you’re applying those skills to, such as databases, social networking, communications, multimedia design, financial analytics, scientific domains and so on. In Mark’s case it’s operating systems. Ya… I’m sure Mark knows how to code, but that’s not what made him a Microsoft Technical Fellow.

An interview with Sam Lightstone, author of “Making it Big in Software”, on Technometria

Listen to an interview with Sam Lightstone, author of “Making it Big in Software” and IBM Master Inventor in this interview on Technometria, as he discusses what it takes to make the most of your career in software. 
Here’s the podcast:

Naturally, the full story is in the book 🙂   See it here:

Listen to Ray Tomlinson, inventor of email, discuss the “@” sign

A short interview I did with Ray Tomlinson, who invented email, asking him about his choice of the “@” sign !

The DB2 Night Show – Sam Lightstone is the featured guest this week

Sam Lightstone, founder of and author of Making It Big in Software will be the featured guest on this week’s DB2 Night Show.

Capture this opportunity to hear Sam live.  Hear an insider’s guide to building a successful career in software.

Register online here:

A career interview with Google’s Director of Research, Peter Norvig

Sam Lightstone’s interview with Google’s Director of Research, Peter Norvig, was on Information Week today. This is a sample from the book “Making it Big in Software”.

A faster horse? When not to listen to your customers

Last Wed I had the privilege of giving a talk at IBM to about 250 software professional. The topic was fostering innovation.  If there is a mantra of the modern corporate workplace it’s probably “Listen to your customers”.  We’ve all seen how companies falter when they try to dictate to their markets rather than listen to them.  However, I truly believe that listening to customers is a cataclysmic error.  By cataclysmic I mean an error so profound it can put you out of business.  Ok, I’m being provocative, to get your attention.  More truthfully, there are times you really need to pay attention to what your customers ar telling you (failure to do so may put you out of business), and there are times when you shouldn’t (because doing so may put you out of business).

Here’s why. Markets are all about supply and demand. They demand products and services to solve their needs.  When people need food they create demand for groceries. When companies need data management they create a need for database software.  Companies need to listen to their customers to understand those needs, so we can supply solutions they’ll be interested in consuming.  The problem, and it’s a serious one, comes when we extend that listening solutions.  The market provides demand, it is not designed to provide innovation. That’s our job as engineering companies.  When we listen to our customers’ ideas about how their problem should be solved it often cripples our potential for dreaming up a more creative and potentially superior solution.  Henry Ford was the founder of the Ford Motor Company and the father of the modern assembly line and industrial automation. He famously said “If I’d have listened to my customers, I’d have given them a faster horse!”.  Apple co-founder Steve Jobs once made a similar point, saying:   “A lot of times, people don’t know what they want until you show it to them.” 

After my IBM talk someone asked me if I really meant we shouldn’t listen to customer ideas about how to solve their problems. Of course it’s always worth listening, and sometimes what customer think they want really is the ideal solution.  But if you stop at listening, and never get to dreaming, you’ll deprive yourself of all the real moments of innovation that can help change the world and drive successful new business.  Although there are exceptions, as a rule if you are only building and doing what the market suggests you do, you’re going to be a follower, not an innovator.

So, my advice is this: Listen to your customers o and requirements. Do that with a passion.  When it comes to finding solutions, consider their input as just that – input.