I’m in. Yet again. This will mark my 3rd attempt at the Ironman distance triathlon. This time, the venue is Ironman Florida, in Panama City. It’s great because it’s close to home and will provide me will more excuses to go down to the panhandle this Summer!
With my registration comes the need to train. Not that I haven’t been training. The real need is to pay attention and train smart. Note – I’m tempted to say “train right” as a bit of foreshadowing, but I haven’t quite bit that bullet yet.
Week 1 in review:
Swim: I got in the pool. Yay! A total of 1500 meters that day. Things felt good. This is the easiest place for me to get burned out, so I’m going to be careful as to how frequently I visit the underwater hamster wheel. My first triathlon of 2012 will be April at the earliest and no more than 2000 meters, so I’m in good shape for that already.
Bike: I rode just over 80 miles this week. One workout was on a spin bike while the other two were open road, including a 50+ mile ride on Saturday. Nutrition was my only issue on the ride. I should have packed more sports drink, or a couple of packs of Cliff Shot Blocks.
Run: I ran 18.9 miles, with a long run of 10 miles on Sunday. Everything feels good – but kinda feels like slow motion. The 10 miler was averaging around a 9:40 pace. Not bad for my longest run since March.
Weights: I lifted one day, hitting biceps, triceps, shoulders and abs.
Tennis: Yes, I’m still playing tennis through this. I went to drills and had a singles match this week. This totaled around 2 1/2 hours of my “training” this week.
In all, it was just short of 12 hours of athletics. My current concerns are over-training, under-training, and improper training. Geez – I think that about covers it. I’ll be working on a plan for dealing with those fears over the coming few weeks. 51 more weeks to go!
I have been involved in a product procurement project for the last 6 months or so and have been intrigued by a number of SaaS players in this particular market. There are a couple of what I consider to be niche players that have very high subscription fees for the service I perceive they offer.
After looking further at their offering, I believe that they suffer from a diseconomy of scale. They are forced to meet the SLA needs of the highest level company they are selling to, and have to charge everyone else for that complexity regardless of whether they need it. Sure, some services can be partitioned, but when you are talking about service availability, response time, storage capacity, etc you are talking about common services that would be difficult to partition without splitting it into multiple individual services.
Online storage is a good example of this. Amazon S3 is a robust solution for delivering fast access to big storage. But if I’m a company just wanting to remotely store backups for a rainy day – it’s overkill. And there is a company in the marketplace that realizes it:
Specifically, more generalized public cloud platforms can suffer from what we might call diseconomies of scale — they have to do more in order to grow, but as their size and functionality grow so does the cost of their overhead. Because that overhead cost is distributed across a cloud’s entire user base, each user ends up paying for complexity he or she doesn’t in fact use.
Interestingly, we do this all of the time when purchasing software. We buy into things that provide us with room to grow. That works fine for an asset you will own, but when you are purchasing a cloud solution, it makes much less since. SaaS applications are like electricity – the light bulb is on and you’re going to pay for it whether you benefit from it or not. As such, you should make sure that you are purchasing based on a model that maps to your actual consumption. This Backblaze solution is a perfect example of purchasing the right solution at the right price for cloud backups.
Read More -> Backblazes Basic Cloud Storage is 25 Times Cheaper than Amazon S3.