BigLong,
Revolution / Cake doesn't seem to have a branched and versioned repository, test builds or staging environments. Don't think rolling something back is an option most of the time

GetonLock tweeted that a quick fix is to turn your computer clock back by 2 hours.

at the least they would have a develop instance, and you say "hey did you test the change on your dev instance? yeah sure! did you roll back your dev? yeah sure! Ok type up what you did and email it to me with the subject roll back plan"

these are computers we are talking about it, and ever the worst company takes scheduled back ups of their servers.

a 12hour outage shows a major lack of leadership from there tech team and it makes me question the product even at it lowest level like the "ring"

If they cant handle network change, can i trust that the poker software ring is "accurate"?

its actually fixed for me now.

You do really expect a lot from these network guys. Unless they have a project manager or lead developer who maintains the repository and issue tracker I don't think this was the last downtime. I truly believe that dev 1 from Bangladesh commits his changeset to the trunk while dev 2 from Singapore commits his without ever checking out the latest trunk or checking on the changelog before doing so. Again.. only if they do actually have a repository setup.

But yes I agree. In the days of teambox, codesion and co one would think that things like this shouldn't happen especially since we're not talking about a silly app but a poker network that generates rake every second. Or at least it should do so.

The messed up batch file of the auto-updater is a perfect example. That bug has been out there since at least a year and has never been addressed.

How do you guys pay your network team? Please don't say real money.

Of course they don't. They get paid in lock funds.

Obviously the dev's are not getting any revenue share or these things wouldn't happen