4 ms·
What upsets me about DevOps, is I know ops pretty well, but am not on par with dev, and every job that just needs someone to ops work now wants to quiz me about
by totetsu 4y ago
What upsets me about DevOps, is I know ops pretty well, but am not on par with dev, and every job that just needs someone to ops work now wants to quiz me about O(n) before they'll interview. Then I look around at the people who are good at the Dev part and the don't know their way around an os or cloud infra.
- dunno7456 4y agoSame, and seeing companies puting devs in charge of interviewing ops people makes the game even worse.
- tayo42 4y agoThose concepts arent that hard though. Just spend a day and familiarize your self with it. The most important take away from those kinds of questions are, can you pick the right data structure when you need to. Using a list vs a hash map, and will you avoid doing things like nested for loops. Big O just puts into words why you want to avoid those things. Most of the concepts should be intuitive already if you have some experience. Personally I haven't seen an interview go in deeper then that. If your writing a script that will touch 10k servers, the operation is likely already slow. if you throw an unnecessary for loop that iterates over everything and runs something, that's going to a painfully slow script and wasteful.
- analyte123 4y agoBig O is kind of a valid question for ops in terms of response time versus load.