1,032 karma · joined March 21, 2013
It can be difficult to understand your negotiating partner's reasons but having an ally sure helped in this case.
Plenty of founder's spouses are allowed in and have been allowed in our offices. None of them had any hiring or firing power.
He fled to Africa and was running a coffee business as a front. US Marshals flew to Africa, found him, kidnapped him, and put him on a flight back to O'Hare.
More details on his case: http://articles.chicagotribune.com/1999-05-25/news/990525017...
Meanwhile in AWS-land, things are humming along. Using more and more of the AWS infrastructure and removing pieces we had previously built in-house. Getting lots of mileage out of boto/Java/awscli and starting to see a real paradigm shift in how to run ephemeral servers instead of the 700 instances 24x7 approach you refer to above.
I came from running my own servers, floundered for a bit on AWS, built an OpenStack cluster and strongly prefer AWS for simplicity and sheer flexibility of the API. I'm a year in running on AWS and haven't had a single issue requiring any support.
The largest benefit has come from the concepts and projects put out by Netflix. If I didn't see companies like them leading the way, I'd likely be a bigger OpenStack fanboy.
See generally: http://www.cloudscaling.com/blog/cloud-computing/openstack-a...
If you standardize on the lowest common denominator, you lose many of the key features of AWS such as VPC and autoscaling.
The Aha! moment for me came when playing with SimianArmy, the wonderful Netflix OSS project and in particular, Chaos Monkey.
Rather than build redundancy into your system, build failure in and force failures early and often. This will surface architectural problems better than any whiteboard.
https://github.com/Netflix/SimianArmy
Also, check out boto and aws cli.
Some feedback for the team:
This release of Marvel would have made more sense after 1.0.
The authentication and authorization of the entire system still needs work. I've got a proxy apache+LDAP in front now but it's clunky and difficult to understand/modify with plugins for example.
You should integrate Marvel and other plugins into your apt/yum repos.
Finally, keep up the great work! Truly revolutionary stuff and great building blocks for all of us out there working in this space. Thanks.
Not a good first sign.
Some tips:
Set up a complete profile. Put as much detail about yourself as you can muster. Clients will keyword search for their positions, you need to come up.
Take the oDesk tests. Qualify yourself in your field.
Learn to pattern match your ideal clients. For me this is US based and paying with OPM (Other People's Money).
Make the case confidently that you are THE person for the job. Some won't have the budget, that's fine, you don't want to waste your time with them anyways.
Always give 5 star feedback for all your clients on completion of the job. Ask them to leave feedback for you. Try to get as many 5 star reviews as you can. Clients filter on this.
Over-communicate. Share docs on Google Drive. Create diagrams. Email, ask how they want to be contacted. This is your chance to shine. The lowballers can't afford to put this much effort into the job. Make them realize you were the correct choice.
For reference, here's my oDesk profile. If anyone is looking for help in the above areas, hit me up.