Every time I try to prepare for a technical interview, it goes approximately like this:
- Starting point: I know that I need to brush up on my tech skills, and since I haven’t coded anything in a long time, at least see what technologies they are using to figure out what’s the most relevant.
- Look up people I’ll interview with on Linkedin, see if they have Quora, Github or Twitter accounts.
- Inevitably find that one or more of them has a blog.
- Start reading the blog.
- In the very first post, find that I don’t understand at least 5 abbreviations or words or references to a language or framework or concept they use.
- Google the first one.
- Find plenty of links to read – forgo the link to the actual site of whoever created or maintains it and go straight to Wikipedia.
- Start reading the Wikipedia article.
- In the very first paragraph, Find that I don’t understand at least 5 more abbreviations or words or references. Without them, what I’m reading makes no sense whatsoever.
- Google the first one of those.
- Remember from my very early computer science days, when I thought that computer science is what I want to do, that this is the very definition of recursion.
- After trying to read the third definition realize that the number of unfamiliar topics will keep growing exponentially.
- This is hopeless.
- Stop reading, take a deep breath, look what else these brilliant people do, then go to yet another humiliating interview where they expect that I know way more than I do.
- See pretty / interesting things on Tumblr
tinfoilparachute 