This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
The honest truth is that I worked directly with him in the early days of Microsoft from my “safe” perch in big IBM, during the startup of the IBM PC. We in IBM didn’t get it at all, and we insisted on calling the IBM PC a “workstation” which in retrospect sounds like “work” for a bunch of robots at their “stations.”
One such meeting that he set up was with the CIO of the largest consumer products company in Europe. I got a call the morning of the meeting from my assistant (who was also shared with this gentleman) that he was planning to cancel the CIO meeting. Think the equivalent of Proctor & Gamble.
The honest truth is that I worked with Microsoft then from my “safe” perch in big IBM, during the early days of the IBM PC. We in IBM didn’t get it at all, and we insisted on calling the IBM PC a “workstation” which in retrospect sounds like “work” for a bunch of robots at their “stations.” Enlist community of support.
The honest truth is that I worked directly with him in the early days of Microsoft from my “safe” perch in big IBM, during the startup of the IBM PC. We in IBM didn’t get it at all, and we insisted on calling the IBM PC a “workstation” which in retrospect sounds like “work” for a bunch of robots at their “stations.”
Currently, I am the cofounder and CIO of Remesh , which is an AI platform that understands and engages groups of people in conversation in real time. What’s your role in your ecosystem? Aaron: I am Cleveland native, but have also spent time living in San Francisco, New York, India, London, and Paris.
Sponsored White Papers, Webcasts, and Downloads Finally, an easier way for Small and Mid-Sized Companies to Run Their Business Applications: IBM Smart Business IBM From the PC to the Internet to every piece of hardware and software in. . | 01/20/10 Maybe This Isnt Such A Bad Thing *NEW* cdelumpa | 01/20/10 What do you think?
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content