kele

You still need to use some software to do that. Also, the screen is too tiny for VCs.

Why would you think that chess skills should translate into good programming skills?

The article has a major flaw: it confuses productivity with LoC.

At my university it's common to call acyclic, connected graph a tree. We distinguish between rooted and unrooted trees. For example, minimal spanning tree doesn't really have to be rooted, it just has no cycles.

> First, you can't invert a binary tree (as in flip upside down). If you did, you'd end up with multiple roots and since all binary trees are rooted, you'd no longer have a binary tree. It'd be a tree, just not a binary tree

Just because someone wrote on Twitter with limited number of characters that the problem was to "invert a binary tree", does not mean there were no clarification from the recruiter.

> And if they actually meant for you to recurse down and swap left and right on everything, it would dramatically lower my opinion of them because it would make me wonder if they knew the difference between how a binary tree is drawn on a whiteboard vs. how it is laid out in memory.

If you're thinking about making a real structure, I believe you should recurse down and swap. If you don't do this, rotating, joining etc, could be a real pain.

GTD isn't suited well for creative, deep work where you can't possibly determine what the next action is.

If you'd like to read more about it: http://calnewport.com/blog/

That being said, whatever floats your boat ;-)

Why would you think it's a shame? You don't really have to be good at these things to be a decent coder.

"Ice" by Jacek Dukaj

Every time I read a novel written by Dukaj I start feeling smarter. The ideas presented by characters are always worth considering and eye-opening.

http://en.wikipedia.org/wiki/Ice_(Dukaj_novel)