Maybe it’s less about code quality and more about eng quality.
If that line itself isn't enough to tell you he's full of shit you have hopelessly fallen for the myth of his Tony Stark-like brilliance. Do you honestly think he contributes any meaningful engineering work at SpaceX? If he didn't own SpaceX, what about his history suggests he could even be an engineering intern there?
Alternatively, it means the organization is resilient enough to handle it.
The US government has successfully accomplished all sorts of things while having various shitty people at the helm.
Every day there are a lot of software developers on this very website (in this very thread) and elsewhere, with no professional engineering background, nor uphold similar standards and professionalism, who refer to themself as engineer.
Please explain how it's possible to be chief engineer at SpaceX without even working there.
Additionally, anyone being interviewed about Musk can't be said not to have a financial interest in him. Musk doesn't hang out with nerdy rocket scientists in his spare time. He rubs elbows with fellow rich people.
It doesn't take much actual knowledge of rocketry to sound super knowledgeable about rocketry to someone with no knowledge of rocketry. Musk isn't a nincompoop but I've yet to hear anything out of his mouth about rocketry that suggests he could intern at his own company, let alone be seriously considered their chief engineer.
Or don't because it will destroy your narrative and you would rather live in your own bubble of delusion.
I’ll take Tesla engineer’s over 95% of the industry any day.
Let alone Boston Dynamic's demos. Or Disney's stunt robot.
-------
So we're mostly laughing at the wasted effort. Of course it's possible, other companies made humanoid walking robots like 20 years ago.
The other questions, like how to actually make money from them, remain unanswered.
https://en.m.wikipedia.org/wiki/Artificial_general_intellige...
In a few years I think even the general public will be able to understand the difference between Asimo and Optimus. It will be remarkable to see Optimus performing tasks independently.
And those people were right.
You don't need to be a part of any particular domain to effectively audit code.
Clearly it gets rockets into the sky, but something similar is true for all code that hasn’t failed catastrophically yet.
This also leads to interesting practices at times like favouring repeating code over writing separate functions to ensure the flow of reading doesn't jump around and instead always moves forward.
They put the flight software through a lot of hardware in the loop tests, simulating launch. That's probably the main novel thing.
You're still missing the point. It isn't about knowing how rockets work or anything in particular. It's about being able to search for and recognize issues.
I don't know why you think someone would have to know about Twitter's specific implementation of distributed systems in order to inspect those systems for non-twitter-specfifc issues.
Sorry, what was it about my comment you vehemently disagree with?
Such as those which do not meet the standards defined for the particular audit.
Do we know what is or isn't being reviewed? Do we know how much effort is being applied in this process or if there's a defined upper and/or lower bound?
Still, the issues you'll likely encounter inside a car are very very different from the ones you'll see inside a historically grown distributed system serving millions of web, app and API requests. Auditing code is more than analyzing runtime/memory complexity.
Thats not to say it's impossible for Tesla engineers to audit. But I'd imagine it would take quite a bit of time to gather meaningful insight into the landscape and would hardly be an efficient use of the time of senior Tesla engineers.
There are many systems involved in those cars, there's also many people working for those kind of companies who do not solely "work on cars."
>Auditing code is more than analyzing runtime/memory complexity.
I agree.
>Thats not to say it's impossible for Tesla engineers to audit. But I'd imagine it would take quite a bit of time to gather meaningful insight into the landscape and would hardly be an efficient use of the time of senior Tesla engineers.
Take longer than if the team were comprised of Twitter staff or who are already familiar with Twitter's infrastructure and code base? Sure. But that's the case with just about any audit conducted by an outside entity.
In short, experience matters.
Also remember that Telsa runs their own distributed systems to support the connected features of their cars. Certainly that's not the same as Twitter, but it's definitely in the same ballpark.
>In short, experience matters.
Is this based off real experience in the field of auditing?
That isn't at all what I said nor implied.
Fooled? No.
>Perhaps consider that your reactionary post was not quite as "rational" as you'd like to believe, or at least that you haven't yet said what you mean.
What part of any of my comments are reactionary? What have I said that I don't mean? I genuinely don't understand.
Did you graduate with an engineering degree or do you just like calling yourself a "web engineer"?
It can be difficult to critique choices, specially in system architecture, when domain requirements are presented or falsely asserted as 'dictating the choice', but this can be addressed by directing conversations with stakeholders to nail down the conceptual model that has been implemented in architecture style x, and then the conversation is on more equal footing.
Auditing language usage, libraries, development process, etc. are much less domain specific.
They wouldn't have to understand any of it, just be able to identify where and when changes occurred, for later review for any last minute shenanigans.
I'm not personally convinced this whole incident even happened, but if it did, this is what I think would make sense.
-- hn_throwaway_99 https://news.ycombinator.com/item?id=33389128
Here I was responding to a comment "What hubris to think that your system is so complex that other engineers couldn't understand it." Which is still a bullshit assessment of the argument (which the original comment was about) that you need expertise in specific domains to be able to evaluate code, which I agree with.
My comment you quoted above is that I think that there would be a subset of Tesla engineers (just not the ones that, for example, solely focus on driver systems) that would overlap with Twitter's domain.
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.
Would it?
Would it not?
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.
Who is thinking that?
If you spend $44 billion dollars on something, you're going to want to look it over extremely well.
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.
Your video player somehow managed to be worse than Reddit, the perennial joke of web dev.
Not to mention “something went wrong” again and again, maybe by the 4th reload would a linked tweet actually show up for me.
I’m on 25 gig symmetrical fiber with <10ms to my local AWS hub, FWIW
That seems like a purpose-built feature to punish non-Twitter users to induce them to sign up for Twitter and/or use the Twitter app instead of the web UI. It's not a bug but a misfeature.
Any competent engineer can come to understand most any part of the system, but it's going to take minimum several weeks to understand what's really going on in a little 0.01% corner of the engineering shop.
But Musk got started by confounding x.com/PayPal, which does have very similar engineering needs as Twitter. It's not like Musk is a newbie to this stuff, people pretending that he's clueless in this domain just want to feel schadenfreude.
But PayPal was running Oracle on IBM bigiron machines even after Musk left them.
Oracle on IBM big iron is a pragmatic (but expensive) way to achieve a highly vertically scalable database platform. Not trendy at all but also not a bad technology position to be in, even now.
A rocketing share heals a lot of wounds. His abusive management practices might fly at Tesla, or his vision oriented startups. There's ample room for doubt his tactics will get results on a turnaround job like Twitter.
Gotta say, this sounds exactly what they said about Tesla, and SpaceX, and Starlink.
It’s much more comfortable than all the public kvetching
Would be really interesting to see the code base for sure and definitely exciting to modify a code base handling so much traffic… not sure I can recall a fail whale in many years so maybe they did something right or maybe fearing the whale set the large organization into stone code fear
Contrast that with Tesla and ever car is requesting data from Tesla servers and many many different complex interactions with much more complex engineering to accomplish a task and id imagine the Tesla engineering to be pretty impressive… but who knows it probably does not handle the same amount of read or write traffic…
Except the ticket booth is in the middle of Times Square in New York and it needs to serve millions of people per second and be instantly accessible around the globe.
The complexity is in the infrastructure, not in the complexity of what they're serving.
You can giggle along with the anonymous source who wasn't involved if you wish but Tesla collects a rather large amount of telemetry and has all manner of micro services crap internally just like Twitter.
I imagine the Twitter codebase itself is a farcical Rube Goldberg machine. Insert your own how many engineers does it take to change lightbulb jokes.
As part of that process, some engineers received a calendar invite Friday, telling them: “Stop printing, please be ready to show your recent code,” a reference to engineers being asked to show the code they had written in the last 30 to 60 days on their computers.
Sounds like he knows exactly what he is doing. I'd do just that. For an unfathomable amount of the people working at twitter the answer will be zero lines of code.True, but an accusatory calendar invite still isn't a good way to do this. He could find out himself from the commit history/JIRA tickets, with the additional benefit of not putting people on the defensive and making a poor first impression. Then again, relationship building isn't really his style, so this doesn't surprise me.
Yes, collecting telemetry is quite equivalent to making a globally-distributed, many-to-many messaging platform available to everyone in real time.
> For an unfathomable amount of the people working at twitter the answer will be zero lines of code.
One of our most productive engineers left the company with negative several hundred thousand lines of code impact over his career. What would he print out?
> One of our most productive engineers left the company with negative several hundred thousand lines of code impact over his career. What would he print out?
Certainly deleting twitter code is even better than writing twitter code. Zen like nothingness is really neither here nor there, now is it?
Diffs.
And what’s the average salary of these people? $15k/mo? $20k/mo?
Ugh, I bet you're exactly right..
I'd presume Tesla's codebase is exactly the same.
It’s certainly more reliable than the evaluation of the person whose job depends on it being evaluated as correct.
Someone who doesn’t understand engineering at that scale would presume it’s the structure of the if statements. And sure, if that’s what you’re looking for, print out some lines and let a person lacking all context take a look.
You could probably call out the bullshitters, though. They aren't refactoring the code base.
Or the folio patchset. People had a variety of reactions to it, whole lot of energy was spent evaluating that code (which in the end also made it in)
The person whose job it was to make the patch and who has interest in it being correct is not necessarily less reliable than a random HN commenter
You would probably think otherwise if it was your code and some other random commenter with no domain knowledge evaluating it, wouldn't you?
Yeah, I'm sure it's of value to have Tesla engineers come in and spend the 3 months to a year getting enough context with the code base to be be able to produce useful and informed critiques.
> The “idea of Elon being flanked by his Tesla engineers reviewing Twitter code is laughable,” the person said.
It is laughable, and it's just another signal that Elon has no clue what he's doing. Imagine how farcical the whole thing felt to anyone involved who isn't him.