> Engineering as a whole is pretty people-oriented: projects are team efforts and require a lot of collaboration, requirements gathering and user research. Jus

> Engineering as a whole is pretty people-oriented: projects are team efforts and require a lot of collaboration, requirements gathering and user research. Just like the statement about coding, I think that's a tad bit generalized because you can apply this to anything you scale bigger. You can make a big project, involving lots of different people, out of pretty much any skill. Tho that doesn't change the basic "requirements" to be good at a specific skill. A coder can still code an app on his/her own, he/she might need more time, but the whole "additional people" thing is entirely optional in this scenario. Same deal with engineering: It might take more time, but even big projects can be done with very few people. Adding more people is an entirely optional thing to speed up the process. It's for that very same reason that many big projects, involving lots of people, have positions solely build around managing the whole "people" part of the project, leaving the engineers to do their engineering and the coders to their coding. Because that's just how we humans are: We ain't perfect at everything, we can't be because lots of it is based on trade-offs.