I basically wrote the code and the specs and documentation for how the client and server talked to each other.
Sentiment: NEGATIVE
When I started at Microsoft, I was lucky enough to be part of the rise of the client-server paradigm.
I had to actually purchase a book to learn the API and write the client. It was pretty frustrating trying to learn the API and develop a product quickly.
I started out with machine code and assembly language.
All this stuff was done via FTP but the web has put a really nice user interface on it.
I got my first computer in the 6th grade or so. As soon as I got it, I was interested in finding out how it worked and how the programs worked and then figuring out how to write programs at just deeper and deeper levels within the system.
The way that I work is very specific, very thorough, and the process has to be totally clear.
Typically, I work with the script and the director for awhile before, just to make sure we're on the same page.
It's important to know how to operate within the system you are existing in.
So if you're a customer today, the same person who came in to demonstrate the technology for you and helped you architect the solution before you bought it is likely going to be leading the team to help you do the implementation.
The relationship between a client must be 'we.'