RoboCrush.com

We apologize for the recent Beta lockdown and hiatus on the blog but we truly believe in the mantra “better safe than sorry”. I’m sure most of you got that from the testing training you’ve gone through.

Probably to many of you we seemed a bit paranoid and it may have even seemed like we were on a witch-hunt. Rest assured that wasn’t the case at all. Sometimes we got a bit careless with the language in the memos we sent out which gave the impression that we were being accusatory.

The truth is the whole problem started with what we thought was a potential vulnerability in our repository of test data. Even though the data itself is essentially useless without the system interface, there was a remote potential of partial reverse-engineering if certain potential exploits we thought we identified were actually present.

As it turns out, they weren’t so now we are ready to return to business as usual.

In the spirit of RoboCrush we will be sending out feedback forms to get your suggestions on how we might have handled this situation better.

Once again let us thank you all for hanging in there during these exciting times at RoboCrush.

Tad & P.J.

Just a quick update to thank everyone who’s been going through this weeks training.

Once again everything is looking great.

We’ll have a fuller update tomorrow as we’ve been tied up in meetings all day.

Well, it’s been an interesting weekend to say the least.

In order to get ready for the first phase of beta testing we’ve been busy reviewing the troubleshooting software and ticketing procedures, including a systematic way and structured way to name the incidents.

We’ve come up with a system based on alphanumeric prefixes, random middle numbers, and alphanumeric suffixes. That will be explained in the initial instruction sets we send out for review.

We’ll be starting out by developing some “mock” errors in order to first test the beta testers knowledge of the reporting procedures, including the incident-report naming convention we’ve decided on.

One thing that should make it easier is that the programmers have put in drop-down menus for the first and last parts of the incident signifiers.