4 ms·
The hubris is thinking Tesla engineers (who are offered worse pay and wlb relative to Twitter) are coding masters of every domain. I won't even snipe at their o
by sidibe 4y ago
The hubris is thinking Tesla engineers (who are offered worse pay and wlb relative to Twitter) are coding masters of every domain. I won't even snipe at their own software here.
It takes a long time to onboard to a big mature infrastructure that is serving hundreds of millions of users for people moving from a similar company, even longer if your day job is whatever Tesla engineers are doing.
And that's onboarding, not pretending to be an expert which seems to be the role they're taking on.
- Nicksil 4y ago>The hubris is thinking Tesla engineers (who are offered worse pay and wlb relative to Twitter) are coding masters of every domain. I won't even snipe at their own software here. Who is thinking that?
- hnfong 4y agoI think you think that the GP is thinking the Tesla engineers are thinking that :D
- MonkeyMalarky 4y agoOn one hand, you can usually safely ignore 99% of code in a system that does the plumbing in a system and focus on the few key algorithms. It wouldn't be a stretch at all to take one of the self driving AI guys and have them evaluate say, an ML classifier used to flag spam/abuse content. That would be well inside their domain.
- johnbcoughlin 4y ago> That would be well inside their domain. Would it?
- Nicksil 4y ago>Would it? Would it not?
- saagarjha 4y agoKey algorithms to do…what, exactly? Why not just read the documentation on that instead of having people bring you a random sample of their code on paper?
- naasking 4y agoWho said they're evaluating the code? Maybe they're evaluating the people by asking them questions about the code they've just written. That's a great way to find out who's full of shit.
- saagarjha 4y agoWhy the printouts then?
- naasking 4y agoSo they can have the code on hand while interviewing them, ask about the code, why they made a certain choice, what other options were available, etc. Have you never had an interview with code printed out or otherwise provided for discussion?
- saagarjha 4y agoUsually we both have copies on our computers.
- ceejayoz 4y ago> It wouldn't be a stretch at all to take one of the self driving AI guys and have them evaluate say, an ML classifier used to flag spam/abuse content. Facebook has a years-old bug with their ML classifier used to flag spam/abuse content in Facebook Groups. Its exact behavior has morphed over time as they flailingly attempt to fix it, but for several straight months that behavior was "posting to a Group via the Graph API fails with 'unknown error' if it includes a dollar sign". This in an API used by tens of thousands of apps and many millions of users, at one of the richest (in both money and programmers) companies on the planet. ML is often a black box "computer says no" scenario with little meaningful ability to debug.
- Turing_Machine 4y agoYou don't need to be a "coding master of every domain" to recognize shit code.
- arrow7000 4y agoIs there any reason to suspect that there is shit code at Twitter? Or that that is in any way related to the problems that Twitter has or the "problems" that Elon said he wanted to fix?
- Turing_Machine 4y agoThere isn't any reason to expect that there isn't shit code, either. If you spend $44 billion dollars on something, you're going to want to look it over extremely well.
- saagarjha 4y agoPay and work life benefits are generally independent of technical competence. But I agree with the rest of your comment.
- onethought 4y agoKnowing enough to call bullshit is way lower than knowing enough to contribute meaningfully to a codebase. Even just having access to code while someone talks I can prove with much higher value questions on what they are saying… because even if I’m asking something dumb it prompts a deeper explanation.