2 ms·
I wonder if it's possible to avoid sub-teams of a project at this scale, could everyone working on it have a general understanding of the entire system? even wi
by micromacrofoot 2y ago
I wonder if it's possible to avoid sub-teams of a project at this scale, could everyone working on it have a general understanding of the entire system? even with imperfect understanding, individual contributors would cover the gaps for each other.
Are there full-stack engineers? or are the individual domains too complex compared to coding?
- _moof 2y agoThis isn't really possible on a project like this. There are just too many specialties, and you need folks who have deep expertise in each one. Just off the top of my head there's structures, mechanisms, fluids, propulsion, avionics, dynamics, software, integration, systems, instrumentation, test, operations, human factors, and manufacturing, and each one of those has sub-specialties. In avionics for example you've got RF and power (among others); in software there's embedded, flight, ground, and interfaces (again, among others). There's a chief engineer whose job it is to oversee the project but they will be relying on the expertise of the individual teams, and each team has to work closely with and lean on their partner teams. Sometimes you'll have people who are cross-trained - I have experience in avionics, software, and ops - but that's not typical, and it doesn't take much to feel spread thin (I certainly do).