Method-X

Hasn't this always been the case in every scientific field? It seems like every other week there's a new study that proves something everyone intuitively knew. The point of doing the research is to gain actual scientific data (e.g. mathy stuff, as you put it) via the scientific method that will add to a preexisting body of knowledge.

Odd. I have a (used) Audi A4 and it's been the best car I've ever owned. For the past four years, the only issues I've had with it were two flat tires.

The assets traded on the bitshares exchange are derivatives backed by the value of the BTS token. This is how counterparty risk is eliminated. Bitsquare is like openbazaar but only for cryptocurrency. Personally, I'm very skeptical the approach will work in practice.

His advice is to work on things you enjoy. The more you enjoy it, the more you learn. Cliche as it may be, it's still very sound advice.

People still publish sites for the love of it. That never changed. Not every site has ads.

What about putting a small banner / notice right above the code editor that explains the user must register before executing code? I'm honestly not intentionally trying to create an annoying site, it's just when you have users running code you legitimately have to take some security precautions. I'll put some thought into how I can communicate this to the user... My favorite idea so far is to just let the user execute code X number of times and then prompt for registration.

Also a really good suggestion. Thank you.

Its focus is on teaching and learning, not getting hired at a big company. Hacker Rank / Leet Code / Code Wars are essentially talent scouts. They want to attract programmers who are already really good. Nothing wrong with that, but it's not conducive to learning.

This would make for a great anti-spam mechanism. Kind of like the ultimate captcha. If quality / spam ever (inevitably) becomes an issue, I will absolutely require a minimum REP / XP.

Hey wjvdhoek, I'm the guy working on this project. I agree mandatory registrations are indeed very annoying (and 95% of the time completely unnecessary). My reasoning behind requiring user registration is for security. Since code is being executed on my server, I want to be extra careful.

That being said, you have an idea I never thought of. I could simply let any user make X number of attempts and then prompt for registration. It's not as annoying that way and still secure. And yes, it's definitely hurting conversion BUT I couldn't think of any other way to set things up. If anyone else has suggestions on this, I'm all ears!

It's more hard sell. HN responds better to soft sell.

Great post. You would really like Peter Thiel (read Zero To One).

Not a chance. Expand where?

Every time code is run/checked it's done inside a docker container. This allows me to set up an environment for as many languages as I want and unit test them. The containers run for a maximum of 2 seconds so if there's an infinite loop, the container is destroyed eventually anyway.

Please do! And if you can, let me know what their experience is like: matt@edabit.com

As for the lack of community, the site has been live for about a week now and it's already got 1000 registered users. In a few months I think it will be very active!

I really hope some people find this to be a fun tool. I spent a little over five months building it by myself.

Before anyone asks, yes, the backend currently supports other languages! Specifically:

* C

* C#

* C++

* Elixir

* F#

* Haskell

* Java

* JavaScript

* Objective-C

* OCAML

* Php

* Python

* Ruby

* Rust

* Swift

Once I’ve smoothed out the rough edges and squashed some bugs, I’ll begin working on rolling other languages out. Also, the challenges right now are rather easy BUT the system allows anyone to publish their own challenges: https://edabit.com/guide/creating-challenges. So if you want harder/more challenges, by all means please help out! :)

You should consider entrepreneurship. Climbing a corporate ladder is only one path to "success".

Here you go:

http://react.semantic-ui.com/introduction