[moritzwarhier]

It's funny how I agree with your post, still switched from "full stack" to frontend, have studied at university and still there's a disconnect.

I've never dived into DNS and it's mostly a black spot in my knowlesge about weg technology basics.

OTOH, I agree with your point in that I've often been very disappointed with the lack of basic knowledge about HTTP and request/response lifecycles with BE as well as FE developer colleagues in the past.

I still would advise against mashing all of this together. Knowledge needs practise.

E.g., I learned about IPv4 CIDR at some point but just never really utilized the knowledge, so it's mostly gone.

Being a generalist is hard.

Of course this is no excuse for lacking basic knowledge (e.g., what code runs where)

[pcthrowaway]

As a front-end specialist you really don't need to know about anything about DNS though, unless you're doing front-end for a domain registrar, openDNS, or a cloud provider with DNS services.

I'm perplexed that there are full stack seniors who wouldn't know about this though.

[1vuio0pswjnm7]

As a web user who relies on controlling DNS in order to "block" ads and telemetry, among other things, and having done so since before "ad blockers" existed, I have long theorised this is why DNS is continually effective for me in successfully avoiding web developer shenanigans. Generally, DNS is a blind spot for web developers. And it appears likely to remain so for the forseeable future.