| > Like before there was doubts he was technical. Now it's clear he is not and was acting (at least regarding software) ... He lies, he gets caught up, that's it Says you, random HN poster. Here's the assessment of a NASA astronaut who spent time on the ISS and who has a PhD in mechanical engineering and a degree in applied mechanics: "[Musk is] able to have conversations with our top engineers about software, and the most arcane aspects of that and then he'll turn to our manufacturing engineers and have discussions about some really esoteric welding process for some crazy alloy" But sure, him and the software engineers at NASA are all dumbasses who are fooled by an actor. Happens all the time. Again - do you guys really think this will work? You are saying what you want to be true, not what actually is true. It's really not necessary. You can loathe the guy for political reasons and still accept that he is in fact an engineer, and does in fact know how to write software. These things are not mutually exclusive. As for "he lies, he gets caught up". Really. Nobody making this claim is in in any position to attack someone else for getting caught up in a lie, given how brazen this claim is, how many people with direct experience have lined up to say the exact opposite, and how obvious it is that it can't be true given his achievements. Please, stop claiming Musk isn't technical or that Gwynne Shotwell is the real leader of SpaceX. It doesn't work and makes all criticism of Musk look like ideologically motivated reasoning. There are plenty of genuine ways to criticize Musk! Attack him for being way too over-optimistic about FSD in Tesla cars if you want. Attack him for requiring logins to Twitter. But don't spread obvious lies about him - it lowers the credibility of all criticism. |
Or this: > I personally wrote the first national maps, directions, yellow pages & white pages on the Internet in the summer of 1995 in C with a little C++. Didn't use a "web server" to save CPU cycles (just read port 8080 directly). Couldn't afford a Cisco T1 router, so wrote an emulator based on a white paper.
Or maybe this: > I mean, man, you’re in charge of the servers and the programming and whatever,” Brown continued. “What is the stack, Elon? Take me from top to bottom. What does the stack look like right now? What’s so crazy about it? What is so abnormal about this stack versus every other large-scale system on the planet, buddy? C’mon!
To which he answered: > Jackass
Or this: > They took one look at Zip2’s code and began rewriting the vast majority of the software. Musk bristled at some of their changes, but the computer scientists needed just a fraction of the lines of code that Musk used to get their jobs done. They had a knack for dividing software projects into chunks that could be altered and refined whereas Musk fell into the classic self-taught coder trap of writing what developers call hairballs—big, monolithic hunks of code that could go berserk for mysterious reasons.
Again I’m not speaking for rocket science, but as for software engineering and ML it seems he only has surface knowledge but does enough name dropping to maintain the illusion.