About services, uptime and agility

Posted by Body on februarie 13, 2009
Filed Under Muncă, Tehnologie | 2 Comments

(Cugetarea saptamanii – nu stiu de ce e in Engleza, asa mi-a venit…)

In ski, they say that if you don’t fall, it means that you have not tried enough. Is this true for desktop products as well? What about services?

I think it all comes down to how fast you can get up, and start skiing again. For desktop products it’s harder, as if you fail one release, you have to pay a lot for a dot release. This does not mean that it does not happen. With DW for example, I think that CS4 was one of the few releases where we did not do a dot release.

But what about services? What if you break something? How long would it take you to fix it? An hour? A day?
I think that with services we have the enormous chance to take more risks. So what if we have some downtime here and there? How many customers will you lose because of that? After all, even services like Google can afford to have some downtime (45 minutes?) from time to time…

So – would you prefer to be the safe skier who is always bypassed by the more courageous ones, or would you be willing to take some risk, learn faster, be better, win it all?

Bogdan

P.S. My shoulder still hurts one month after my last skiing experience :)

Share

Comments

2 Responses to “About services, uptime and agility”

  1. miChou on februarie 13th, 2009 16:48

    What’s a dot release? :D

  2. Body on februarie 13th, 2009 18:15

    De exemplu Dreamweaver 8.0.1, care a fost lansat dupa Dreamweaver 8.

Leave a Reply