I spent a few years writing down my thoughts about how one should approach problems. If you're looking for a how-to guide, a cookbook, or a reference this book is not for you. If you want to learn by challenging the way you think, pick up a copy.
I've been using these computer things for a while. I've written what is now over 100k lines of production C code and many thousands of lines of code in a variety of other languages. I've seen my software run and I've run other people software. One thing they all have in common is their propensity to break under unforeseen circumstances. Shit happens.
On my laptop, I don't care much. I want nice, I want convenient, I want new and pretty and productive. I'm willing to tolerate a nominal amount of instability for those desires. I have to reboot my Macbook Air at least once every month to accommodate general software failures and security updates. There is, after all, a lot of crazy software on my workstation. (yes I call my laptop a work station as it is the station at which I work -- how many of your do the same?)
Somehow, somewhere some engineer and their cult following decided that they wanted to make a datacenter operating systems be more desktop friendly and a product manager somewhere and their hefty company decided they wanted to make a desktop operating system be more datacenter friendly. I would care so much about those decisions if they didn't constantly screw me. This stops now.
I don't want sound drivers and X11 or gnome in my datacenter operating system. I don't want the kernel developers considering how priorities and implementation decisions effect software that has no place near my database server or web server or load balancer. I don't want my scheduler to be optimized for browsing the web while watching a video. My server is to serve the Internet.
We've been working on something to scratch our itch at OmniTI. If you are pissed off like me, maybe you'll like it... coming soon.
I bought tuna, fake crabmeat, ikura (salmon roe)... I had nori, but it was aged and inseparably stuck together.
If there is one rule to live by, it is this: bacon makes everything better.
Here's the plan. Take a shrimp (40-50 count) and put it on a cutting board. Take half a length of regular bacon and wrap it into an open cylinder with the shrimp as the base. Bake in an oven (from cold start) at 400 until crispy (about 20 minutes beyond preheat). If your bacon is too thin cut, it might deform badly in the oven, so consider inserting a ball of tinfoil to help it keep its shape. This is what you have:
Now we have a platform for the beauty of the sea. At the second local grocery store, I was able to find sushi-suitable tuna loin, wild salmon roe and (of course) imitation crab meat.
I coarse chopped some tuna, mixed half with Sriracha for the adults and left half for the kids. From there I made four types of baciri (bacon nigiri -- yeah, that's mine): tuna, spicy tuna, ikura, and crab + cucumber. Served all this with slices of avocado on the side. The nice part is that the salty-fatty-smokiness of the bacon provides umami and there is no need for soy sauce.Boom. Magic.
Because this was clearly a "deep south" meets "east" kinda meal, I tied it together with a bowl of brussel sprouts cooked with bacon and a bit of chicken broth and a bowl of szechuan green beans ("sautéed" in bacon fat from the sprouts).
The little timeout I am taking to write this note isn't sufficient to dive into the truly interesting things my readers usually expect. However, I'd be a jackass if I let you go any longer without knowing that Surge is going to be friggin' awesome this year. At the end of this year, if you look back and see that you missed attending Surge you'll know what regret truly is. Just sayin'.
My opinion is that the only reason the big enterprise storage vendors have gotten away with network block storage for the last decade is that they can afford to over-engineer the hell out of them and have the luxury of running enterprise workloads, which is a code phrase for “consolidated idle workloads.” When the going gets tough in enterprise storage systems, you do capacity planning and make sure your hot apps are on dedicated spindles, controllers, and network ports.
It was fantasy believing it was possible to pull off a centralized network block storage service in a multi-tenant cloud without any of the architecture shenanigans our enterprise brethren do and think that applications, databases, and business could depend on its being perfect. Honestly, we should have know better. We the applications developers asked what is perhaps the crappiest of all abstractions in computers to solve all of our availability problems for us. We asked for magic. Clearly, the vendor never should have made the promise of magic, but everyone is to blame for this continued expectation that such magic is possible.
The CFPs have been rolling in for Surge 2011; these are exciting times. It does, however, appear that our description of what we're looking for has produced a different set of submissions that what I expected. I think it might help to better understand what sessions were like last year and, luckily, we'll be releasing all of the Surge 2010 video footage this week. I apologize for the poor audio quality, we intend to pull in A/V recording professionals this year.
We've received some great proposals! However, a surprising amount of them are presentations about products. This conference is about problems and their solutions. It is a conference for practitioners by practitioners. Blood... in the mud. I want to (as we did last year) share our struggles for better collective experience.
Emphasis: Accepted proposals will demonstrate real-life scalability challenges and creative solutions. We love case studies and learning from our mistakes.
As such, with this context, I'm extending the Surge 2011 CFP deadline to April 17th.