Technical and non-technical tips for rocking your coding interview
<i>2. What happens between you typing a URL into your browser address bar, hitting enter and seeing a web page?</i><p>"What happens when I'm asked a question like X?  I spout a mutated form of some canned response I cribbed from a list I found on HN a while back.  Because I hear that's how you're supposed to 'rock your coding interview', these days."<p><i>3. What are the things you should consider if you were writing your own database server?</i><p>"Look, you know as well as I that this job has nothing -- as in, <i>nothing whatsoever</i> -- to do with actually building production-grade database servers.  Or anything even remotely analogous to it.  Debugging that tangled mess of poorly conceived, never-reviewed JSON APIs left behind by the other developer (while you were pestering them about 'disruption' and 'just needing to get this thing to market') is more like it."<p>"But hey, since you're playing that game, I can play too:  here's a bunch of catchphrases like 'non-blocking I/O, sharding, blah blah.'  Because I hear that's the killer answer to give to questions like these.  And BTW, if you really think that people Michael Widenius or Salvatore Sanfilippo would be interviewing for this job, then your problems are way bigger than I could ever hope to help you with."