Rojo – how not to publish updates to your site
Rojo has been my favourite on-line reader for a while despite the annoyances and quirks but this weekends ‘upgrade’ got me wondering how incompetent the team behind it is and what exactly Six Apart have purchased.
There were a couple of problems before the upgrade – the one most users would have seen is the crazy unread counts which are almost always wrong – but you can learn to live with that.
The second problem was Rojo failing to pull feeds in – if you drill down and there’s nothing to read you are given the “This feed is failing” message which tells you zip about what they think is wrong.
In the case of DamienG.com’s RSS feed I was told by their support staff this was because they couldn’t connect to my server. GrinGod created a feed to my site’s Atom feed that *was* still updating so that excuse was shot down quite quickly.
It’s not just me either – major big blogs such as blogs.msdn.com would sit for hours with the same message before springing back into life.
Then came this weekends upgrade.
I have some experience with publishing code to commercial sites. This is the sort of plan we use:
- Install and configure secondary set of servers
- Load software to be tested onto those servers
- Let internal testers loose on them
- Let trusted end users loose on them
- Run load testing software to ensure performance
- Repeat until it passes
- Schedule the switch with the appropriate teams
- Make an announcement
- Switch over to the new servers
But the team at Rojo went with a different approach. As far as I can tell here was theirs:
- Take current servers off-line with a notice
- Load software for 20 hours
- Bring servers back on-line
I certainly don’t see testing on that plan.
“Show unread only” may as well read “Show nothing” as that’s what it’s doing.
These aren’t boundary conditions but primary use-case scenario’s that are failing.
To cap it all now every single feed has disappeared in the last half-hour.
It has been reported that Rojo have raised at least $3.5 million in venture capital so why their software development process looks like an inexperienced developer publishing from his laptop is anyone’s guess.