3 ms·
These numbers often get inflated because the people in change count every part-time worker as a full team member (bigger headcount = bigger promotion!). But it'
by teaearlgraycold 3y ago
These numbers often get inflated because the people in change count every part-time worker as a full team member (bigger headcount = bigger promotion!). But it's still a crazy number. At every level everyone is incentivized to bloat the headcount as much as possible.
- dylan604 3y agoIt’s basically “I caught a fish this big” story where each telling increases the size
- azemetre 3y agoI don't think part time work in SWE is common at all. Especially at Google. The 400 number is likely including product owners, business analyst, designers, etc into those numbers not strictly being SWEs (happy to be proven wrong).
- teaearlgraycold 3y agoThat's not what I mean. At Google you can be 50% on one project and 50% on another.
- tylerhou 3y agoYou can but it’s not common either (across orgs).
- canucker2016 3y agoFor a comparison, initial Windows NT 3.1 had 340 devs/testers, NT 3.5 had 530 devs/testers. No idea why product/program managers aren't listed. There must have been some. See https://danluu.com/microsoft-culture/ https://danluu.com/microsoft-culture/
- xrayarx 3y agoDoes anybody know how MS does Windows development these days? Just curious…
- gumby 3y agoI hope someone at Microsoft does, though their attention seems to be elsewhere.
- midoridensha 3y agoI'm guessing around 800: 3 devs for the OS core, the rest for the adware and spyware. (/s)
- azemetre 3y agoThat's good to know, honestly surprised to read that NT had that many. I'd figured early versions wouldn't require that many people. Now knowing the Fuchsia numbers, I don't know if that's a signal to how productive the team is or if they dwindling resources.
- heavenlyblue 3y agoAnd also for comparison, Windows NT 3.1 had to run and interact with a much broader zoo of devices.