As OP said, you would not be able to google the specific B-Tree question because if you don't know about B-Trees you wouldn't know that you need to google it.
There's a difference between things you know you don't know (and therefore can google), and things you don't know you don't know (and therefore will not google).
What? Not everyone works on front-facing, UI applications. What if I contributed a good amount of code to a large tech company's networking infrastructure. What do you want me to show you? A picture of the servers? A picture of Amazon's homepage or google.com, if those are the companies I'm working for?
Not being able to show "code" or "screenshots" is not the fault of the prospective employee (as you "oh so subtly" implied with your last sentence).
Congratulations on your success. There so many comments here on what you could or should have done differently. I know you'll read it and maybe you'll give some of it a try. But if what you are doing works for you, then keep at it. When you stop making gains or want to switch up your program, you know what to do. Thanks for documenting all your tips and what you have learned. Keep lifting.
Do you mean it's a lot of work to type in that prefix? Because vim automatically inserts it for you when you enter command mode while something is visually selected. A making a visual selection is very quick and easy.
Why was this posted to HN? He's been getting some attention because he was hired by Yahoo, so better remind everyone that he was immature and annoying when he was 15! Can we really blame him? Who wasn't immature when they were 15. He'll grow up, we don't need to bring up someone's every flaw every time they achieve success.
There's a difference between things you know you don't know (and therefore can google), and things you don't know you don't know (and therefore will not google).