The "VMware" experience
I've been wanting to write about my time at VMware for quite sometime now. I thought I should write when I have plenty of time so that I could do justice to it. But that just never happens. So I decided to write now ... when a build (compiling and linking) is going on.
There have been very few instances so far when hype and huge expectations have been matched by the end product. The two most recent ones were the Twenty20 World Cup in South Africa and the IPL. But there has also been one more such instance, one from a completely different league ... VMware!!
Learning about and yearning for system software has been something I've done for years. Right since the first time I was introduced to it (Big Big thanks to a visiting professor in my undergrad college who taught us Microprocessor Based Systems), I've been in awe of it and have wanted to know more and more about it. I have to say that working at VMware has not just made me learn much much more, but has left me craving for more. To say that working in VMware has been an outstanding experience would be a gross understatement.
The idea behind the formation of VMware was pretty simple. I like to put it this way: "Why would you have just a sigle operating system running on a computer at any given point in time? If I can have Firefox and Internet explorer running simultaneously on a computer, why can't I have both WindowsXP and Linux?" ... {I hope I am not totally wrong here. It would be really embarassing to praise the company you work for only to find out that your basic understanding about its fundamentals is totally incorrect ;) }. To achieve the above, VMware introduces the layer of virtualization between the actual hardware and running operating system/s. This layer allows running multiple operating systems (called "Guest Operating Systems") to run simultaneously on the same hardware.
So as one can make out, VMware's work is very close to the hardware on one side and the operating system on the other. Thats precisely the reason some of the biggest geeks from around the world found this idea to be awesome and have been working hard on it. It feels special to be in the company of some of them.
Quite a few people here eat, sleep and breathe technology. Discussions about Operating systems, drivers, processors, instruction sets, etc. are very very commonplace. The two most commonly heard words are "VM" and "Guest OS". In a span of just about a decade, its amazing what VMware has achieved. From being a company with an outstanding idea to being the 4th largest software company in the world, VMware has had a fine run for the last 10 years.
I still remember the first time I saw a "virtual machine". It was simply amazing. The fact that you could see an OS inside a small window, just like you see any other application was really really special. I did harbour thoughts of being in VMware then. Today its a reality and I feel proud of it.
I hope VMware keeps doing just as good as it has been doing (not lately... but over the last 10 years) and scales new heights. A few millimeters from that height might be because of me ;)
There have been very few instances so far when hype and huge expectations have been matched by the end product. The two most recent ones were the Twenty20 World Cup in South Africa and the IPL. But there has also been one more such instance, one from a completely different league ... VMware!!
Learning about and yearning for system software has been something I've done for years. Right since the first time I was introduced to it (Big Big thanks to a visiting professor in my undergrad college who taught us Microprocessor Based Systems), I've been in awe of it and have wanted to know more and more about it. I have to say that working at VMware has not just made me learn much much more, but has left me craving for more. To say that working in VMware has been an outstanding experience would be a gross understatement.
The idea behind the formation of VMware was pretty simple. I like to put it this way: "Why would you have just a sigle operating system running on a computer at any given point in time? If I can have Firefox and Internet explorer running simultaneously on a computer, why can't I have both WindowsXP and Linux?" ... {I hope I am not totally wrong here. It would be really embarassing to praise the company you work for only to find out that your basic understanding about its fundamentals is totally incorrect ;) }. To achieve the above, VMware introduces the layer of virtualization between the actual hardware and running operating system/s. This layer allows running multiple operating systems (called "Guest Operating Systems") to run simultaneously on the same hardware.
So as one can make out, VMware's work is very close to the hardware on one side and the operating system on the other. Thats precisely the reason some of the biggest geeks from around the world found this idea to be awesome and have been working hard on it. It feels special to be in the company of some of them.
Quite a few people here eat, sleep and breathe technology. Discussions about Operating systems, drivers, processors, instruction sets, etc. are very very commonplace. The two most commonly heard words are "VM" and "Guest OS". In a span of just about a decade, its amazing what VMware has achieved. From being a company with an outstanding idea to being the 4th largest software company in the world, VMware has had a fine run for the last 10 years.
I still remember the first time I saw a "virtual machine". It was simply amazing. The fact that you could see an OS inside a small window, just like you see any other application was really really special. I did harbour thoughts of being in VMware then. Today its a reality and I feel proud of it.
I hope VMware keeps doing just as good as it has been doing (not lately... but over the last 10 years) and scales new heights. A few millimeters from that height might be because of me ;)
posted by Shri at 5:00 PM
2 Comments:
From what I know, the basic idea really was to increase server utilization. So it was about being able to run multiple independent "jobs". But for that to be used in real world, you needed to have the "jobs" isolated. Mainframes had solved that problem using Virtualization, so trying to apply that to the server was how VMware came about.
I remember the chat we've had about VMware right when you had the two competing offers-one in NY, the other in VMware-and I'm glad you took VMware...
Cheers!
Post a Comment
<< Home