Hi everyone,

I am finished with phase 1 of my web app. It is a website devoted to providing robust statistics about your game play. I am opening this up for open beta testing so feel free to sign up, check it out, see if you like it, and provide feedback. Thanks!

https://www.chessalytics.com

Hi Jason,

I'll be pleased to take a look in a few days.

Are you willing to say what you used for implementation? I've been doing some work in Perl, but the heavily nested structures JSON generates aren't as pleasant to work with in perl as they might be. On the other hand, all the excellent portions of perl (including my almost 30 years experience with it and very easy database integration) continue to be in its favour.

I'm beginning to think a module or else module-per-endpoint might be the way to go; hide all the awkward bits (and they are merely awkward to read) behind a nicer interface and call it done.

Thanks for making your beta application available!

Giles

Says it's not working.

Esta página não está funcionando

www.chessalytics.com não consegue atender a esta solicitação no momento.

Thats fixed, thanks for letting me know!

Man. Everything fell apart really, really quickly. Will let you guys know when its working again. Really frustrating.

OK, everything back to working. Learned a few things about EC2 instances the hard way.

@skelos its just your everyday ordinary php.

Thanks. I've once rewritten an application in PHP; nothing wrong with what the first guy did except that his code was full of security holes.  But he created a UI users of one of my programs wanted that I didn't want to write, so the users won in the end.

Mind, I did mutter about scope creep as I was being paid to add a feature to the pair of programs (my backend, more than the UI) but didn't feel able to ship the old UI code with security holes I learned about while working on it!

Unfortunately this isnt going well.

When I originally tested the actaul data pull I tested against around 30 players data. I stopped testing that a couple months ago when I was satisfied Inwas getting all of the data. Now for some reason its bombing. I see a lot of stuff in the JSON now that I didnt see originally and also it appears I didnt test against anyone who actually played any tournament games (admittedly Inplayed in very few but was getting the tournament games OK in my personal data - now it seems thats bombing too).

Guess I have to go back to the drawing board. 

You said beta test. Alpha test is when it works for some cases some of the time. Beta test is where you want use cases you're not so personally familiar with tried.

Sounds like that happened. It's a successful test by that sort of definition. Everyone in this group is either a developer or hanging out waiting for news of cute new applications. No shame in something not working.

Indeed, as I presume you were not/are not being paid for it, no shame if you decide, "Interesting, but I wanted a week long project, not multiple man-months."

If it helps, my most successful project ever came to need version 2.0 due to a change in its environment. I took three tries to design and implement the replacement. The first two totally bombed: each time the design was more complex than I could handle and the minimum test time for anything was 15+ minutes due to the ancient hardware I had access to.

Version 2.0 attempt #3 rocked.

I signed up. That's a really neat idea.

Looking forward to the progress!

Well, I have a plan to fix it. I understand the problem and should at least get the data functionality up and running within a few days. Other bugs found so far: subscriber game records appearing without a corresponding subscriber record, and confirmation emails not firing off. Give me a few days and will message to the community when I am ready to start again. Thanks to everyone who has tested!