Several hours from now, I will have entered the first level of the Shaolin of AWS. I've been studying for almost three years at the foot of my elastic ninja master, monkey coding in the fields. Now I approach formal gates and turn my experience with the raw into gems. Mysteries abound. Patience will be rewarded.
In parallel, I am also moving in other certification worlds. I will be pursuing my Amateur Radio license next month, and by the end of October, I will become a CERT adjunct to the local fire fighters in my town. In multiple dimensions, I am embracing disaster, death and rebirth. I am conforming to the shape required to hustle people past, around and through tragedy - the end of things most of us know to be inevitable, but avoid.
It's odd to notice the 1000 ways to die. Did you know that you need to approach burning cars from the sides? Because the bumpers are on shock-pistons that might suddenly expand in the heat and break your legs. Can you look at a building and tell how it might collapse? I'm going to survive. I have little doubt in my mind, but how is the interesting part. Survive and let the upside take care of itself.
I have come to the point, and I'm about to step over it, where I find it amusing to build code in my spare time. So I have ideas and plans. Maybe this year I'll do something loud. It will be official.
As for the AWS, the more I brush up against its culture, the more I have to take seriously the fact that the fat client and proprietary interface world is moribund. Once you accept that the sophistication and overload of HTTP protocols is just inevitable, the more you take as legit the enormous amount of unstructured data that needs to be dealt with. I don't actually feel like expounding on it so much as learning more Mechanize and Nokogiri. See?
I expect that I will be combining a lot of API level stuff and orchestration this year. Lots of SNS and SQS and SWF and hand-built CLI. Damn, I need a web guy.