Sunday, 26 January 2014

An Important Life Skill - How To Make A Works Burger


Today (26th of January) is Australia Day. As this is the case I think it important that the knowledge of building a Works Burger is shared. This delicacy should not be only be available for those from the Antipodes. So here is the 12 step process to build your Works Burger. If you feel that this sounds like too much to attempt, rest assured that the effort required, results in sheer joy and immense satisfaction at having climbed such a behemoth! (For proof of this look at the sheer joy in the last photos of this post!)

Step 1. Get a bun. Preferably very large.


Step 2. Add Tomato, Mayonnaise or BBQ sauce. This one is your choice. It's freestyle


Step 3. Add the burger, with melted cheese and bacon. Some call this step 3, 4 and 5. However for recipe simplicity and to remove the sheer terror of the recipe I combine into one step.


Step 4. Add a slice of pineapple. The order is important here, as will become apparent in the next step.


Step 5. Add a runny fried egg. So you can see here why order is important. If the egg breaks, the pineapple ring provides a well for the yolk to collect in, as opposed to squirting out the back of the bun on first bite.


Step 6. Add fried onions


Step 7: Add fried mushroom


Step 8: Add salad leaf. This is an incredibly important step. It's important to eat your greens.


Step 9: Add beetroot. Order again is important. Beetroot should be last in this process, as will be explained in step 10.


Step 10. Add the top of the bun. So the beetroot order is important, as by adding it last, the beetroot juice that squeezes out, is soaked up by the top half of the bun. Again it doesn't squirt all over the shop when you take your first bite



Step 11. Celebrate the behemoth that you have created. Look at the sheer joy on that face! However this is the daunting thing. At this stage you have actually only climbed half the mountain! The second part of the climb is actually consuming the beast!

 
Step 12. Eat 


Some suggest there is a step 13, although amongst connoisseurs this is often debated. However if you have managed to make it though step 1 to 12, then quite often a step 13 is required, which is sit still for a long period of time. This is sometimes required as it is difficult to breath, or indeed be active in any way, shape or form, post consumption.

So now you know how. Now you know why - again look at the joy it brings. Now go ahead and create. You will no be disappointed!

Cheers

m
 

Thursday, 2 January 2014

Why Are Carriers Not Supporting Developers?


It filled me with great sadness when I visited the BlueVia Developer Portal yesterday to find that all developer APIs have been removed from the site. I used to work with the BlueVia team and for some reason we were unable to make a business case out of supporting access to Telefonica resources to developers.

I had been campaigning without success to expose developer APIs to all DT resources - something that Developer Garden does for developers who want to engage with DT's German customers - for ages before moving to BlueVia. BlueVia for me was a chance to succeed at providing simple access to carrier assets i.e. SMS and Voice services. We had limited success with BlueVia Voice in that we were able to launch a beta service to provide access to these services for a limited number of developers. Unfortunately I was not able to convince those that needed to be convinced that there was a business case that would support the necessary investment required to make the service profitable.

At the same time. companies like Nexmo on top of $4.83 million in funding are now expecting total revenue of around $40 million for calendar 2013. According to Crunchbase Nexmo:

Currently seven of the top ten messaging platforms rely on Nexmo to route SMS and Voice calls to over 200 countries globally. The Nexmo platform handles over 250 million messages a month, with 20 percent growth monthly.

Wondering what the monthly growth in Carrier SMS is? Well here's a hint, unfortunatly mobile carrier SMS is peaking and starting to decline :-(. As I've long campaigned carriers have not innovated on SMS since it's invention, other than offering increasing bundles of SMS to Customers. It is developers who will lead any growth within SMS usage, but they will only do this via services that provide simple access to it. It is only the OTT players who are providing this access.

Another example is Twilio - who were on track for 50 million in revenue for 2013.

While Mobile Carriers are failing to expose their assets to developers, OTT players continue to grow and engage with developer hearts and minds.

Ho hum.

Cheers

m