binofbread

Just a heads up: https://singleops.com/contact/join-our-team/ is a 404 for me.

Would it not be possible to write a contract that has intentionally random results? Could you not use the timestamp or some other piece of data to flip a coin to determine the outcome?

Does the EVM prevent this in some way?

I did some searching but I'm not sure I know what to look for either.

Clicking on the "Features" link in the footer under "Navigation" takes you to /faetures, which of course is a 404!

The title is a bit misleading in my opinion, but it was a good success story nonetheless. Congrats to Brad and the team.

Edit: By title I meant subtitle. I think it was changed on HN.

Just FYI, the image at the top doesn't look that great on my retina display!

I see. It was very confusing to click "Sign In" then click "Don't have an account? Enlist Now." and be redirected to the home page. Looks cool though, thanks.

Edit: I now see the intended flow, but there was no indication that I had to complete the first 2 levels to be able to sign up.

I would love to sign up, but when I click to create an account, I get redirected to the home page.

My hand cannot do 9 the way you describe. My pinky is too stubborn.

I'm running into a similar issue and fairly new to angular. In fact, the tutorial I followed even set up the server calls to use the _id field when looking at a specific model (ie leagues/{{ league._id }} ). What's the proper way to go about fixing this?

Well said, thanks for the insight.

I don't think learning Rails right now is a bad thing. I've been doing some side projects in it for ~2 years and definitely don't regret it. As some other folks in here have mentioned, there is always going to be something newer and better out there. If Rails is your first or even one of your first web stack experiences, it is a great way to learn the fundamentals and it makes learning the next new thing that much easier. In short, the "next big thing" is ever changing and I don't think anyone would call Rails old. It's just no longer new.

His argument is that the "new paradigm" is constantly changing and reinventing itself (usually with old concepts). Meaning in ~2 years, there is going to be a "better" way to do things. I'm not sure I agree with him, but that's his argument for not switching to a front-end MV* framework.

He seems to be in the "if it works now, why change it?" camp. So at the moment that means using Java Server Faces on the front end. I haven't had much exposure to the server-side, but I'm so not sure there is any good framework in place as it's closely coupled with the front end logic.

Your second comment is a good one. What I think he meant by "trend" was that last year Rails was what all the architects and leaders at the company were pushing for. His argument was that this year it's the same thing except with single page architecture (Backbonejs in this case).

We're a decent sized tech company. I have actually read that, but I had forgotten about it. Thanks for the reply and pointing me back to the article!

Very cool. Scanning the source code makes it look like you were using Alpha-Beta pruning[0], but I'm not totally sure why the function is named 'pvs'. Does anyone have a quick explanation?

[0]: http://en.wikipedia.org/wiki/Alpha%E2%80%93beta_pruning

I believe this is set by default in oh-my-zsh as well.

As a 21 year old, it took me a second to realize that was Steve Jobs. He looks so young.