chibicode

Thank you! I've written a follow-up article: https://news.ycombinator.com/item?id=21484016

Thanks for the comment!

> not a very simple one with all the "labels" and "numbers" etc.

I understand this concern. I did have quite a large number of non-technical people do the Japanese version of this course (I have a big following in Japan), and they seemed to actually understand it based on the feedback I got.

The course itself doesn't use any code and is not very fast-paced compared to this article: it spreads out the material covered in this article in 17 pages and takes about 2-3 hours to read.

> I wonder if this visual presentation of lambda calculus is your invention

It's my invention (spent a year tweaking the details) but was inspired by things like Scratch. https://scratch.mit.edu/

I’m the author of this article—ask me any questions! :)

Thanks :)

A few hours every night for a week :) But I'm not a dad, haha.

Yes, I am going to implement pagination next (with React)!

Sorry about this, it might have to do with JSBin. I reported it here. https://github.com/jsbin/jsbin/issues/2464

Thanks! Looks like the issue is with JSBin embed. I reported it here:

https://github.com/jsbin/jsbin/issues/2464

Will investigate! Sorry about this.

Edit: It might have to do with JSBin. I reported it here: https://github.com/jsbin/jsbin/issues/2464

Thank you :) Totally agree, I knew Angular coming into React and it threw me off quite a bit as well.

I'll add a link to it :)

I totally agree, in fact I'm going to link this :) The point I wanted to make is that every feature requires a bit of refactoring like this, whereas React puts some structure.

Thank you :) !

Thanks and oh no, do you know which browser/OS you're using? Not sure if it's the JSBin thing...

Edit: I think it has to do with JSBin. I reported the issue here: https://github.com/jsbin/jsbin/issues/2464

Thank you so much! :) I also found that a blog format is much easier to consume than a REPL/in-browser editor based one.

Awesome :) Glad to hear that!

Yup, I agree... will fix! Thank you!

Yup, React does one thing, does it right, and does the right thing :)

Thank you for reading!

Thanks! I definitely should put more in the next steps, like examples/talks/etc. I wanted to ship this asap :)

I wrote how we use ZenHub at our startup here: http://devblog.edsurge.com/scrum-kanban-trello-github-issues...

Seems relevant: "App-pocalypse Now" by Jeff Atwood http://blog.codinghorror.com/app-pocalypse-now/

EdSurge (Burlingame, CA), an edtech/news startup, just raised $1.5MM and is looking for a software engineer. Details: http://careers.edsurge.com/software-engineer/

I definitely agree that for a startup team, Github is making CS interview questions extinct. Even github itself claims so: http://ozmm.org/posts/who_we_hire.html - "at GitHub we hire "The Girl or Guy Who Wrote X," where X is an awesome project we all use or admire."

However, it is a different question if you are running a company like Google or Facebook. For instance, recently there was a news that Google received > 75,000 applicants and is looking to grow by more than 5000 employees this year. http://goo.gl/9fpkt

If you want to scale at this level, you won't have time to look at Github or similar sites for every candidate in detail. There will also be great candidates who have never published their code (although they might be the minority). To maintain hiring standards in this kind of situation efficiently, asking very difficult algorithmic questions might be the only way to go - at least you will be able to maintain the same hiring standards for 75,000 applicants.