On the other hand, I consider v8 the most extreme optimized runtime in a weird way, in that there’re like 100 people on the planet understand how it works, while the rest of us be like “why my JS not fast”
270 karma · joined May 1, 2015
My principle has always been: “is this part a isolated and intuitive subroutine that I can clearly name and when other people see it they’ll get it at first glance without pausing to think what this does (not to mention reading through the implemention)”. I’m surprised this has not been a common wisdom from many others.
Another question is, what motivated you to start this effort in the first place? And why do you think it's useful. I haven't read the book, so not really sure
Not all people are interested/capable of learning how it works underneath. There're like, I don't know, hundreds of thousands of React developers in the world, very few of them understand how React really works underneath.
This is actually one of the goals that React was invented and popularized inside Facebook. It's just sooo easy to pick up and start building.
That being said, for our product, it's not only about React and its basics. We can totally create a workout project for React internals. That depends on what you guys need :) We started with these two projects because it seems a common useful and popular thing, and we're able to do them ourselves.
> That said I don’t often get asked for source code during interviews these days, so probably the ability to host the minified code for a demo would be enough.
I'm a little bit confused about this piece. Are you suggesting we host the minified code on our site + the demo? Because in the first part, I thought you wouldn't want that because employer should see this as a tutorial thing if they see anything on a third party website other than your own website?
Sounds like a good idea to provide a free trial. But I also want to make sure that people are actually interested in paying.
What specifically do you mean, by "how the spec is laid out, and how the solution is laid out"? I guess I understand the spec part, but what about the solution?
The from-university statement, so true, it's an art. We're trying to explore to find the perfect balance :)
The homepage is actually sorta old. I'll update it.
On the job seeking perspective, what you said is right. Typically what people do is signing an NDA, but even with that, the question/solution still sometimes leak on the Internet.
On the learning scenario, it's sorta true, but mostly sharing the solution would ruin the motivation, at least for me personally. If I know there's a solution sitting there, I wouldn't be interested in repeating it again.
I know it's sorta silly... But my mind works best when I only focus on the problem, and how to solve it. As long as I know there's a solution, I couldn't stop myself looking at it whenever I was stuck at any tiny bit.
What's your thoughts on Kaggle? Is it similar?
As for examples, we do have some examples of separate tasks (non projects) in the tasks page, that should explain how things work really well.
We were originally thinking since you need a computer to actually do the project, so didn't bother making the mobile version at the beginning.
A lot of the challenges here is really close to what we do as developers.