4 ms·
"Full-stack" is very vague and very rarely means working on the full stack. Also, if someone cannot answer the question: "what happens when you type 'google.co
by partycoder 11y ago
"Full-stack" is very vague and very rarely means working on the full stack.
Also, if someone cannot answer the question: "what happens when you type 'google.com' in your browser" then you are definitively NOT full stack.
- fishnchips 11y agoAh, the Google interview question. Should we start at keyboard interrupts? ;)
- V-2 11y agohttps://github.com/alex/what-happens-when#the-g-key-is-pressed https://github.com/alex/what-happens-when#the-g-key-is-press...
- partycoder 11y agoShould we start at the motor cortex?
- fishnchips 11y agoOnly if we're recruiting a neurosurgeon.
- beeboop 11y agoI think it depends on the context, and that context has shifted a lot over the past ten years. I can deploy an app to Heroku that scales tremendously well (if expensively) and have almost zero knowledge of configuring a web server or the tools it uses. I think it's probably more accurate to define "full stack" as being able to make and launch a web application on your own. Servers and databases are just tremendously easier than they used to be, so the bar has been lowered a lot. Knowing the steps of what happens after typing in "google.com" in your browser is only relevant to people working on projects of massive size, in which there is no need for a "full stack developer" in many cases, or you're doing something completely removed from just a web application.