Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Huh? You guys just launched - why would you immediately try to migrate to some new technology you have never used? Don't you have other technological and user facing issues to face before you start optimizing the back-end?

For example, what's up the with http://ticketstumbler.com/charlotte-bobcats-playoff/ that?



Actually, barring errant issues such as that, our biggest pain point by far is the back-end. There are a few bugs still around, yes, but they are within acceptable norms for something "just launched". The new back-end is a big part of what will fix issues like the one you've pointed out (not to mention the current cause of them). The more stable it is the more it can be relied on to automate fixes such as this and other bugs that crop up; click around long enough and you'll find a few other easter eggs! Sorry to ruin your fun, but I am aware of all of them.

There's a significant difference between optimization and getting something where it should have been in the first place. All of our user facing issues such as links that go no where, stale tickets, etc. are all in one way or another caused by the back-end. All the TS front-end does, really, is display data. It takes almost no input, other than what you search for. There's no user data. A well-trained seal could make it bug-free.

TL;DR: No.


TicketStumbler knows the Bobcats won't make the playoffs for another ten years and is simply testing our users' savvy.

Just kidding - thanks for pointing that out. Our biggest user issue, like my favorite female body part, has to do with the back end.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: