“Code” is most likely “architecture” and “architecture” is code for “management”.
Of the engineers I've met, I'd put the Tesla ones as 'smarter'.
but I have inspected plenty of organisations where strong engineering teams are drowned by management bullshit. even found places where most of the individuals, engineering and management both, are arguably competent but the overall organisational decreptitude kills any and all effective work, no matter how heroic or skilled the individual and collective effort gets.
I get twitter has some issues of scale to solve, but its tweets, even netflix would be far more challenging imo.
Tesla engineers likely are drinking the Kool-aid or were not talented enough to get offers at better companies.
Lastly, it's not "just tweets" at their scale. That's like saying Netflix is just storing some video files in CDNs.
I’m not a software engineer (data scientist) and I’ve only managed up to 15 people, but if a friend who worked in a factory asks me to review a CTO of a team of 50, I feel confident I can say “Asking people to write their own unit tests isn’t abuse of power” and “Asking people to be behind their desk at 9 am or risk pay cut would not fly anywhere else” — things that he might not have the context to know.
Sure, there might be a new paradigm that I’m not familiar with where devs don’t write unit tests, but I’m fairly confident if I hear about that, I can ask questions and see why it’s more efficient.
A really good (reverse) example of that is James Douma. Several Tesla commentators rely on him to comment on Tesla’s AI announcements. He doesn’t work at Tesla and confesses that he might not be able to lead the AI team there, but he’s personable, clear, and familiar enough with ML to offer some judgment on why things are done in a certain way. He’s usually very positive but he could easily be asked which teams don’t seem to be executing as well, and what questions to prod them.