Snips and snails, and puppy dogs tails
That’s what little boys are made of!
Sugar and spice and all things nice
That’s what little girls are made of!”
Have you ever heard the phrase: “It takes all kinds to make the world go ’round?” Well, it does. Especially in Information Technology. But, I’m of the opinion that IT people come roughly in two flavors.
- Technicians (or Engineers)
- Consultants (or Analysts)
What’s the difference you say? Well, here’s my definitions:
Technicians are technical. They understand the *how* of a technology, how to make it run, how to service it, install it, create it. They’re great with machines, coding, and complex troubleshooting. Often they’re the kind of people that just can’t stand to *not* know why something broke and want to fix it no matter how long it takes.
Consultants look at business process and are more interested in why and where and who and what rather than the how of a particular technology. They may also be very technically capable, but they generally marry superior customer service, business analysis, and communication skills with that technical capability.
Here are some common questions I’ve heard about technicians and consultants:
Q. Can you train technicians?
A. You can give people knowledge about a technology, but it’s much harder (if not impossible) to train the intuitive grasp of *how* technology works. Contrary to what most people think, the creation, operation and support of technology is as much an art as it is a science. It changes so rapidly and the complexity is so overwhelming that if all you have is book knowledge and you don’t just “get it” you’re not going very far. This is one of the real advantages young people have in growing up with technology that their parents did not… they just get it since they’ve been dealing with it their whole lives.
Q. Can you train consultants?
A. You can train consulting skills for sure. You can teach people to look at business process and to consider the business implications of using one technology or another. You can train people to be good with customer service and you can educate them in the use of written and verbal language skills. But, once again, there’s a certain something that separates good consultants from technicians. You have to not only “get it” the same way a technician does but you need an intuitive grasp of how people think and how they interact with technology.
Q.Can a technician become a consultant?
A. Certainly! I did! I think we all begin as technicians. You only develop an ability to see the larger picture and the business savvy required for consulting over time and with experience. It requires development especially of your communication skills, both verbal and written. If you didn’t learn to spell and your grammar depends on Microsoft Word’s spell checking you’re in for a hard ride as a consultant.
Q. What’s wrong with being a technician?
A. Absolutely nothing. We need both technicians and consultants. Technicians do things with the actual technology that consultants just can’t. Someone has to make this stuff! Someone has to code the applications and build the servers. But would you put a technician in front of a client and ask them to deliver a presentation to C-Level management? Definitely not. It’s not a good use of their skills and they probably wouldn’t enjoy it.
So, which is better? Technician or Consultant? It depends on your business needs. And since I’m a consultant, would you like a presentation on the topic?
CIOs and IT managers are slowly realizing the benefits of Cloud Computing but there’s still a long ways to go. Product offerings for hosted services have matured and exploded but there are so many options now that it’s hard for IT management to keep up.
So, here’s a quick guide to the Cloud technologies that are out there. I’ve broken it out in to the three major Cloud services areas to help you better understand what’s available and how:
- IaaS (Infrastructure as a Service) or HaaS (Hardware as a Service)
- PaaS (Platform as a Service)
- SaaS (Software as a Service)
Infrastructure as a Service
* In a nutshell: you pay for full access to a server that someone else hosts for a monthly fee. These services generally include some sort of terminal access to a virtual computer instance that you populate with your own operating system and software license. Often, you’ll access the server through a terminal service client of some sort. *Note: HaaS often is confused with IaaS and generally refers to on site (not Cloud) equipment provided along with support services by a service provider for a monthly fee rather than as an up front capital investment.
* Who needs it: anyone that needs full configuration capability for a server but doesn’t want to actually host the server themselves.
* Benefits: host equipment so you don’t need to build your own Tier-1 datacenter for access to a highly reliable and secure environment.
* Challenges: even though you have full access to the “box” your applications are deployed on the “box” may actually be a virtual server rather than a full server… limiting the configurations on the actual hosting hardware. If you’re trying to move a locally hosted server to the Cloud the performance may not be the same since your connection now goes over the internet.
Platform as a Service
* In a nutshell: highly-reliable hosted operating system software that totally obscures the hardware infrastructure. Services may be accessed through a web browser or application client of some sort.
* Who needs it: application developers that need a platform (.NET for instance) for their applications but do not require complicated customized infrastructure. Anyone who wants their application to “scale” quickly on a fully virtualized platform without downtime for software and hardware upgrades.
* Benefits: the infrastructure disappears. You get a reliable and scalable service for a monthly fee.
* Challenges: customization of the platform may be restricted to enable broad use by many types of applications. You may not have all the options you would like. Some PaaS services do not provide all the debugging, test and development tools you’ll need or may use tools you’re unfamiliar with.
Software as a Service
* In a nutshell: perhaps the first and most recognizable of the cloud services, SaaS obscures the whole back end and simply provides a web-based application generally accessed through a web browser.
* Who needs it: anyone wanting to host a highly reliable web site or service generally accessed through a browser like Internet Explorer or Firefox. Some applications may be quite complex and may even interface with hosted databases and other web services but require no access to the underlying operating system or hardware on their own.
* Benefits: the cheapest and least complex platform and also the easiest to develop for. Applications can be deployed very quickly.
* Challenges: configuration options are often accessed through a web console and are limited in scope.
There’s something for everyone in Cloud computing. With so many options, the question is not whether you need Cloud computing any more, but WHERE you need Cloud computing. Many companies are taking baby steps in to the technology through obvious Cloud computing targets like hosted e-mail and CRM. Especially small and medium sized companies that have difficulty investing capital in secure, highly reliable onsite infrastructure will be interested in the opportunities that Cloud computing presents.
Even large enterprises can find Cloud computing synergies. How powerful would it be to pay a monthly fee for an application you don’t need to deploy across hundreds or even thousands of desktops? Wouldn’t it be nice to simply deploy a shortcut to a hosted application instead? There would be no need for internal development and no need for additional help desk resources.
If you’re a CIO or IT manager, do yourself a favor. Get educated and get moving. The Cloud is here like it or not.