FIRST Server Issues

[nixiebunny]

This is why I have a cushy part time job... to be able to waste an hour griping about a failed registration system on social media.

But seriously, I assume you can pay a testing company to slam your site with 5000 pretend registration attempts in two seconds. If I ran a website like this, that's the first thing I'd arrange for.

[SGK]

Their new server consists of all the returned Samsung Galaxy Note 7's!! --- Just Kidding!!!

[Andrew Schreiber]

Originally Posted by nixiebunny

This is why I have a cushy part time job... to be able to waste an hour griping about a failed registration system on social media.

But seriously, I assume you can pay a testing company to slam your site with 5000 pretend registration attempts in two seconds. If I ran a website like this, that's the first thing I'd arrange for.

You can do it yourself with a bit of work. There's a handful of tools out there for it. Tsung is the one I've seen folks use in the past, but I've never had much of a need for it myself.

[marshall]

Originally Posted by nixiebunny

This is why I have a cushy part time job... to be able to waste an hour griping about a failed registration system on social media.

But seriously, I assume you can pay a testing company to slam your site with 5000 pretend registration attempts in two seconds. If I ran a website like this, that's the first thing I'd arrange for.

Pay someone for it? That's what testing suites and tools are for. Simulating load these days isn't difficult.

[Lil' Lavery]

Not sure what all these "shoulda, coulda, woulda" posts are really accomplishing.

[ScoutMom700]

FIRST Facebook page reporting registration is postponed to next week.

[synth3tk]

Originally Posted by AllenGregoryIV

we aren't expecting them to be perfect but they could also provide far better service to their customers and not wait 45 mins before making any public update.

👀

This.

[marshall]

Originally Posted by Lil' Lavery

Not sure what all these "shoulda, coulda, woulda" posts are really accomplishing.

They are users being frustrated. It's what people do when things don't work out the way they expect. It's ok and it's a good thing. If someone hits on an idea that helps make it better in the future then it is worth it. The important thing is that everyone have some empathy with the IT gals and guys working this problem at FIRST HQ. Sometimes things break and we need to be patient and understanding about it... that doesn't mean we can't lament/complain/grieve/hypothesize publicly.

[notmattlythgoe]

Originally Posted by Lil' Lavery

Not sure what all these "shoulda, coulda, woulda" posts are really accomplishing.

Not sure what all these "Not sure what all these shoulda, coulda, woulda posts are really accomplishing" post are really accomplishing.

[nixiebunny]

Originally Posted by Lil' Lavery

Not sure what all these "shoulda, coulda, woulda" posts are really accomplishing.

They accomplish the venting of STEAM.

[FrankJ]

Site seems to work now.

(No, registration is not open)

[marshall]

Originally Posted by FrankJ

Site seems to work now.

(No, registration is not open)

Nice editing... smooth.

[David Brinza]

Originally Posted by Lil' Lavery

Not sure what all these "shoulda, coulda, woulda" posts are really accomplishing.

Agreed, but FIRST not anticipating this possibility (given prior history AND the new website) by having "Plan-B" ready to go isn't acceptable.
The email blast announcing a postponement should have been sent an hour earlier. I'm pretty sure the writing was on the wall 10 minutes after opening.

[Lil' Lavery]

Originally Posted by notmattlythgoe

Not sure what all these "Not sure what all these shoulda, coulda, woulda posts are really accomplishing" post are really accomplishing.

My hope was to transition the thread towards a more positive tone (and as Marshall said, more empathy towards the IT folks who are surely very stressed at the moment). I see now that my attempt was only mildly successful, at best.

[Trying to Help]

Originally Posted by iyportne

I know this is unfortunate, but as a continuous improvement professional I know none of us have gotten to where we are without backward steps, and I trust FIRST will fix and make good on this process as well.

My bigger concern now is tempering the attitude of my students who may be reading this thread. Some may come away with the idea we should never try new things and take risks to move forward and just keep doing what we are to avoid ridicule should things go wrong.

Remember, everyone can predict something that just happened, and everyone can solve an isolated issue without the entire context.

Perhaps we can use this thread as a case study for Gracious Professionalism vs. Ungracious Pro-victimism...heaven known we have the evening news for the latter.

I am not ridiculing FIRST. And I know that we all make mistakes. Sometimes those mistakes have lasting, serious consequences. This is thankfully not one of those instances.

This is a professionally created tool that is an essential part of the FRC process. As such, the robotics community has reasonable expectations that FIRST upholds their portion of the implicit agreement. We postpone work, schedule lunch early, have someone cover for us, etc. We will now have to do it again for next week. And for those of us in district competitions, not too long again after that.

It's reasonable that if you try something and fail, people call you on it. I did say that there are plenty of resources out there to help troubleshoot and remediate the problem.