The Next Big Thing
Posts about next generation technologies and their effect on business.

Do you need a technical bucket list?

list.pngI wrote a post about what a technologists can do to be relevant a while back and at the time I thought that a list like this would be relatively transient. It turns out that unlike buzzwords, the underlying technologies are usually here for the long haul -- just ask a COBOL programmer. The half-life of the experience is likely much longer than I thought.

 

I was in a discussion today where we talked about a list of experiences a technologist needs to have in order to talk with some degree of authority about the next big thing in an enterprise context. Naturally, a person can’t know everything to the same level of depth, but there is a basic, useful level for every strategic technologist to have.

Some of the obvious ones I’ve mentioned before were:

  • Install a public cloud-based virtual machine and use it for something
  • Write an application for a mobile device and get the app listed in the app store
  • Take an on-line class (or maybe a couple every year) through a tool like coursera

A couple of those items would have been as applicable 2-3 years ago as they are today. Some have changed quite radically in their capability in that timeframe. I’ve done each of them at least twice for one reason or another and each time I learned something new.

 

If I were to add a new one that I haven’t touched in a very long time, it would likely be something to do analytics. There is a bit of a problem with this one though, since having enough data to do something useful and interesting may be tough.

 

I mentioned I was going to experiment with 3D printing. I now need to find something in the Internet-of-Things space as well.

 

I’ve probably looked at all these things enough to understand what their good for, but actually tackling a project brings that perspective to a whole other level. The hands-on experience doesn’t need to be production ready quality, since the goal is as much generating the exposure to the issues and ideas as it is solving a particular problem.

 

What other areas should a technologist tackle? And how? I haven’t even mentioned anything in the networking space. Anyone who has looked under the covers of Software Defined Networks probably knows the depth of impact changes in this space will have for the future.

 

The book Outliers talked about spending 10,000 hours on an area to become great. I wonder how tackling 400 technology domain experiences allows you to be successful - that’s 10 a year for 40 years.

Leave a Comment

We encourage you to share your comments on this post. Comments are moderated and will be reviewed
and posted as promptly as possible during regular business hours

To ensure your comment is published, be sure to follow the community guidelines.

Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.
Search
About the Author
About the Author(s)
  • Steve Simske is an HP Fellow and Director in the Printing and Content Delivery Lab in Hewlett-Packard Labs, and is the Director and Chief Technologist for the HP Labs Security Printing and Imaging program.
Follow Us