San Francisco, CA (2 min wlk from Caltrain) FULLTIME REMOTE H1B

★ Full stack JavaScript Engineer (Backbone/Knockout/Express/Node) ★ at Gild.com

We're rethinking the way professionals find great companies to work for and apply for jobs. We believe that the current process is broken for both applicants and companies, and we're fixing it. We're venture-backed (Globespan, TMT Investments), and our customers are crazy about what we're building.

This position is our first technical hire dedicated to our new Node.js infrastructure, with a ton of room to influence its evolution. The best fit will be someone with hands-on experience working with a production Node.js app. This is an amazing opportunity for somebody who is passionate about JavaScript technologies.

We're looking for somebody that can translate a high-level product vision to production-ready code without needing a babysitter.

Technologies we like: Javascript/Coffeescript, Ruby, Perl, Express.js/Zappa, Socket.io, Sprockets, Rails, Compass, SASS What you don't know, we will teach you. What we don't know, you will teach us.

Cool things we've built: http://youtu.be/13GaYDoRwOg

Apply here http://goo.gl/SX4sW

(Please don't apply if you suffer from the "Not invented here" syndrome. We like lazy coders.)

and if you're a programmer we will donate $5 if you solve our programming puzzle on http://fightsopa.org

Thanks!

Yup, your script should receive the path to a single file, not a wildcard. I'll take a look at the logs. :) Thanks for your feedback.

Works now, thanks!

Great!

It's a fairly easy puzzle, for an average programmer it should take at most half an hour. Give it a shot :)

That's valuing my time at $10 an hour. No grazie:-)

Sure in this case you better send them the 5$, nevertheless please share this with friends or colleagues that may want to give their contribution while having fun for half an hour.

By the way, if you're an experienced programmer the solution is quite obvious, it should take less than 15 minutes. :)

and on Coderloop you can also use Fortran, Erlang, Objective-C, Lua, Javascript, Scala, OCaml, Clojure and Common-Lisp :)

http://www.coderloop.com/home/guidelines

thanks, I've posted the video because the sysadmin puzzles are not yet available to every user

the video shows how they work, any feedback/comment is welcome :)

Yeah, I got to the site and noticed that. Bummer, I'd like to give some a try.

I wrote a note on the post but it doesn't seem to show up. We have the puzzles for sysadmins in beta and we're looking for beta testers, send us your coderloop username to info@coderloop.com and we'll enable the feature for your account.

Hi, I'm the founder of Coderloop.com, a programming competition platform. Our platform is able to test user submitted programs against a problem spec. We also support specs that require the user to write a program that interacts with an HTTP server (an example here http://www.coderloop.com/puzzles/islands ). If you are interested we can build some puzzles dedicated to your API. :)

Interesting, thanks.

The scope for my contest would be more loosely based than solving a specific problem criteria, although that could be an added fun twist! I anticipate people would build apps for phones, plugins for other software, services to help users, etc. Many companies run competitions of this nature, e.g. Twilio.

I could run off some ideas for what's needed if you'd be interested in expanding Coderloop to support a contest like this?

I'm sorry for that, we're going to add support for 2.7 very soon!

Upon further reflection, it may be that you're loading the code dynamically or something (and not just running it as a command line application) or something that caused the __main__ not to trigger.

Once I understood the constraint, I was fine. It's a neat little app, and for somebody who's never had an actual job as a programmer, some of these exercises I feel are things that I should at least know the pattern.

I'm digging it.

Thanks! The code is executed by an "host" script with a system call, not sure if this breaks the __main__ function in python. We will look into that issue. :)

Hi, I understand your point. The problem with the feedback is that if we tell you for which inputs we're testing your solution, you could develop an optimized version of the solution for those special case, or worse you could precompute the solutions and just write a solution as a long if-then-else sequence. The purpose of the challenge is instead twofold: being able to understand the problem specs and being able two produce a generic solution that must work in an environment that you don't control (because that, at the very end, is what happens to the programs you write... They're going to be executed with inputs that aren't under your control and that you couldn't know in advance).

In theory, I agree with you.

In practice, I have spent an entire week during a universitary course with various problems from such problem site and eventually learned that the problem descriptios were different in a subtle way or certain edge cases were not considered or the test suites were flat out wrong. (This was particularly amusing, because they had added wrong test cases after certain solutions were accepted beforehand. Thus, It was clearly visible that the problem was solveable, because there were programs accepted).

Also I don't entirely agree with the argument that my program has to work in an unknown environment with unknown controls. In such a situation, I would at least get a logfile to see what was going wrong. Without that, debugging anything non-trivial is just not worth it without getting paid for it.

Ok but here the point is not about technology, it's very easy for us to give you access to the output of your program (in fact if you use a compiled language, and the compilation phase breaks, we show you the log). The point is that any kind of feedback that I give you access to that is generated from the input we send you to you program, will give you the chance to produce a solution that i not generic, because you know the input in advance, you can precompute the solution and just "print" it. You can object that we should generate the inputs randomly and on the fly. That can be definitely done for the very trivial problems (like reverse a string or a sequence) but will be impractical for more difficult problems that have very few input data sets that lead to a "meaningful" result.

Anyway, we're open to suggestions on how to improve the process. :)

Well you have a correct solver to the problem. Couldn't you just randomly generate an input, push it through the certified solver and supply me with the input-output-pair?

For one, even if this is the actual test input you use, I will not know it.

For two, it might not contain the trigger for my errors, but if I can get enough such samples, I should eventually get a sample which contains the problematic input.

For three, from what I see, the problems should be possible to generate randomly, especially if the certified solver rejects malformed input. E.g. for the missle problem, throw together N numbers and look what happens until the certified solver outputs a proper solution.

In theory it can be done, but it would be very expensive in terms of computational power. Anyway, you raised a very good point that we will keep in mind for the near future. Thanks indeed for your feedback and the nice discussion.

I see this concern. I thought a bit more about this during the day. The computational power required could be reduced if you stored the generated inputs and present them to the user if he requests additional help.

Given this, this system could be extended using a rating-system by users ("Click here if this input helped you solve the issue"). This would overall result in a bunch of inputs being generated (basically whenever someone needs a new input), and some edge case inputs will overall bubble to the top, because they are rated helpful more often than others.

Anyway, I'm happy to help. Good luck :)

Cool, this one is a very good idea actually, a user generated database of test cases for each puzzle! I'm putting it in our backlog, thank you very much!