[glasz]

makes me wonder when people will realize that "full stack" and "devops" are great ways to have less persons do more things and save a bunch on salaries. a gold mine for my corp.

[beatgammit]

> devops

Isn't that basically "backend" with lots of experience around automation tools?

I have only worked at startups, so I guess I wear all hats. Here's what I understand:

- frontend - presentation bits, can further separate into developer and designer for UX and logic respectively - backend - APIs, database interaction, concurrency, etc - full stack - backend and frontend - dba - tuning databases - server admin - tuning OS - devops - automation, with a splash of backend and server admin

Does that sound about right? If so, full stack and devops overlap quite a bit, and must full stack should be able to handle devops tasks, so wouldn't "full stack" be sufficient to fill your ranks?

[EADGBE]

My devops experience hasn't been much backend at all. Mostly scripting, server configuration & stand-up, etc. But I consider backend API programming.

[TheCoelacanth]

It doesn't really save on salaries, though, unless the company is so small that it doesn't have enough work to take up the time of both a full-time full-stack developer and a full-time operations person and can replace two people with a single person who does both jobs.

It costs more because someone with both skill-sets will demand a higher salary than someone with only one of the skill-sets.