On: Are You a DevOps Engineer If You Aren’t Writing Code?

[28304283409234]

I spoke to another person calling themselves 'Full Stack Engineer", but couldn't even explain the OSI model.

What's your point? Titles rarely match competences and responsibilities.

[8organicbits → 28304283409234]

Is that really a relevant question? A full-stack title usually means web front-end, mobile, web back-end (or API), and database. Its a generalist title. You work mostly with HTTP, but even then an API framework may hide that.

If you're deploying to a PaaS you may never care about or notice lower layers. If not, your team may have a specialist (DevOps, platform engineer, network engineer) who manages network configuration, DNS, load balancer, connection pooling, firewalls, VPN, and other details.

[cetahfh14615 → 28304283409234]

I mean, in full stack engineering (from my exp) you work primarily with rest and don't ever make use of lower level networking details.

maybe it's different for someone working in networking or a more specific subfield. It might've been different in the past, idk

[mr_toad → 28304283409234]

The “stack” in full-stack engineering used to refer to the software stack, not the network stack.

The old-school eponymous LAMP stack used to be Linux, Angular, MySQL, and PHP. You wouldn’t necessarily have had to have known the OSI model to be proficient in those technologies.

[bdavis__ → mr_toad]

s/Angular/Apache/

LAMP was a term from the 1990's.

[jimz → bdavis__]

And the stack is still used today by plenty of people around the world, what's the problem?