Things I Brushed Up On This Week: The HTTP Request Lifecycle

Too Long; Didn't Read

I have been interviewing recently, and as most devs know, the breadth and depth of questions you can expect to be asked during an interview is pretty much immeasurable. With that in mind, I have been probing recruiters on what I can expect to be asked during technical rounds. Sometimes I find it hard to maintain all the possible categories of questions I can expect straight in my head, let alone the questions themselves. I tend to forget things under pressure, <a href="https://stackoverflow.com/questions/9553628/piping-and-redirection" target="_blank"><em>like that </em></a><code class="markup--code markup--p-code"><a href="https://stackoverflow.com/questions/9553628/piping-and-redirection" target="_blank"><em>|</em></a></code><a href="https://stackoverflow.com/questions/9553628/piping-and-redirection" target="_blank"><em> in bash is for processes/programs and </em></a><code class="markup--code markup--p-code"><a href="https://stackoverflow.com/questions/9553628/piping-and-redirection" target="_blank"><em>&gt;</em></a></code><a href="https://stackoverflow.com/questions/9553628/piping-and-redirection" target="_blank"><em> is generally for files</em></a>. In service of wanting to retain the information better and force myself to write, I have decided to start posting walkthroughs of what I brush up on. I tend to require at least 3 sources to get a complete, correct, and well-written explanation of a topic. I would like to consolidate that for other people.