"Why not also require third-party integrations" - it almost has to include that anyway, but.. the skill set required to understand and work with third-party int

"Why not also require third-party integrations" - it almost has to include that anyway, but.. the skill set required to understand and work with third-party integrations is almost certainly going to be a subset of 'front-end' or 'back-end' anyway. Mastery of client side and mastery of server side are distinct enough that those sort of 'what abouts' you raised seem to fall under the broad 'front/back' domains already, no? There's enough virtualization that 'hardware' itself is a somewhat elastic term. However, I've had to deal with 4 different devs in the last few months, all trying to get set up with one of two projects. Both are docker-based. But... "well, I'm on windows... I'm on WSL... I'm on Mac, but M1... I'm on Mac, but Mojave, and this doesn't work..., oh, I can't have 2 things running on the same port?" Unless every single person is on the exact same hardware/OS combinations, having some understanding of 'hardware and OS diffs' and how they may impact you may still be necessary.