Looking at what you wrote at 15, I'm curious to know what you are doing nowdays?

I co-founded http://www.fitanalytics.com/ as the only technical guy, been working on that for the first four years (started with nodejs 0.4.x back then and CoffeeScript).

Now I have a small team in Berlin (5 devs), doing some mobile apps and a project for Wix: www.wixeducation.com (ES2015, Postgres)

We don't have a real website, because we're so busy :D but there's a logo online: www.code-pan.com

Line 67: ON ERROR GOTO errorhandler...line 205: errorhandler: RESUME NEXT... Obviously, this code has no errors ;-)

Frustrated most of the day! But somehow strangely satisfied.

For a PayPal employee to post here and say he made a team aware and they are working on this it's utterly laughable.

There was a post here on hn over two years ago for the same issue which was top post and generated a lot of news.

https://hackernews.hn/item?id=6526481

It is obviously very well known to them for years but they continue to do it

Obviously well known?

Guy at PayPal sees post, tells a technical person about it, said person forgets about it. Suddenly PayPal doesn't know about it anymore.

Or a person wants to work on fixing this but a manager says no, because there are other priorities.

Or a person starts working on this, quits, and it gets lost among the things they were working on.

It's so easy for things to get lost in a company, even with all the bug trackers in the world.

Isn't this what support case systems and bug tracking software was meant to do - to track non-closed issues?

yeah, I agree, but I think a lot of us work in similar situations, where bug tracking exists, but there's such inundation of bugs that we can lose track of some.

I guess I have sympathy for the PayPal team in this case. They're working on an extremely large product, with a huge user-base. I would imagine it would be very easy for bugs like this to fall through the cracks even with a "process" in place

That assumes that the manager doesn't insist that bugs of age get closed simply because long-open bugs make for ugly metrics.

Is it just me or has there been a resurgence in cinema going as a social activity. It felt like around year 2000 when dvds were peaking and then flat screen tvs came in, cinemas were a lot quieter.

Baseball feels like a next step up. About 2,400 games a year. More games, data points.. more everything

More very old, very dangerous sharks swimming in the same pool. Betting to win long term is not something most people are mathematically or emotionally equipped to do and a toy demonstration showing a handful of results means very little.

Great points. This was just a cool demonstration of the underlying technology hoping to inspire people to use it on their models in domains other than prop betting. Potentially it could help those sharks already swimming in these pools, but our goal is to help every expert in every field make better models.

Great idea! You could reuse most of the code [1] to give this a shot. In future posts we may extend this to other sports as well.

[1]: https://github.com/sigopt/sigopt-examples

I'm glad to see this thread and some debate about react router and it's features and ways it could be better. Too often any react critisism is attacked almost fanatically.

Merry Christmas HN!

Micromanagement is exhausting.. Once you learn to let go just enough to be able to supervise and step in only when you need to, work becomes more fun.

Coder's worst nightmare? When you are the last line before something gets pushed into production, and the fear that it will fail IN production.. have i missed something?