Elektrine lite

← Feed

@feld@friedcheese.us

Post #2233471

2025-02-10 19:22 UTC

@calcifer@hackers.town @shanselman@hachyderm.io > In the evenings, Musk headed to Rocket Science Games, a start-up based in Palo Alto that wanted to create the most advanced video games ever made by moving them off cartridges and onto CDs that could hold more information. The CDs would in theory allow them to bring Hollywood-style storytelling and production quality to the games. A team of budding all-stars who were a mix of engineers and film people was assembled to pull off the work. Tony Fadell, who would later drive much of the development of both the iPod and iPhone at Apple, worked at Rocket Science, as did the guys who developed the QuickTime multimedia software for Apple. They also had people who worked on the original Star Wars effects at Industrial Light & Magic and some who did games at LucasArts Entertainment. Rocket Science gave Musk a flavor for what Silicon Valley had to offer both from a talent and culture perspective. There were people working at the office twenty-four hours a day, and they didn’t think it at all odd that Musk would turn up around 5 P.M. every evening to start his second job. “We brought him in to write some very menial low-level code,” said Peter Barrett, an Australian engineer who helped start the company. “He was completely unflappable. After a short while, I don’t think anyone was giving him any direction, and he ended up making what he wanted to make.” > Specifically, Musk had been asked to write the drivers that would let joysticks and mice communicate with various computers and games. Drivers are the same types of annoying files that you have to install to get a printer or camera working with a home computer—true grunt work. A self-taught programmer, Musk fancied himself quite good at coding and assigned himself to more ambitious jobs. “I was basically trying to figure out how you could multitask stuff, so you could read video from a CD, while running a game at the same time,” Musk said. “At the time, you could do one or the other. It was this complicated bit of assembly programming.” Complicated indeed. Musk had to issue commands that spoke directly to a computer’s main microprocessor and fiddled with the most basic functions that made the machine work. Bruce Leak, the former lead engineer behind Apple’s QuickTime, had overseen the hiring of Musk and marveled at his ability to pull all-nighters. “He had boundless energy,” Leak said. “Kids these days have no idea about hardware or how stuff works, but he had a PC hacker background and was not afraid to just go figure things out.” and > The Musk brothers brought Zip2 to life at 430 Sherman Avenue in Palo Alto. They rented a studio-apartment-sized office—twenty feet by thirty feet—and acquired some basic furniture. The three-story building had its quirks. There were no elevators, and the toilets often backed up. “It was literally a shitty place to work,” said an early employee. To get a fast Internet connection, Musk struck a deal with Ray Girouard, an entrepreneur who ran an Internet service provider operation from the floor below the Zip2 offices. According to Girouard, Musk drilled a hole in the drywall near the Zip2 door and then strung an Ethernet cable down the stairwell to the ISP. “They were slow to pay a couple of times but never stiffed me on the bill,” Girouard said. > Musk did all of the original coding behind the service himself, while the more amiable Kimbal looked to ramp up the door-to-door sales operation. Musk had acquired a cheap license to a database of business listings in the Bay Area that would give a business’s name and its address. He then contacted Navteq, a company that had spent hundreds of millions of dollars to create digital maps and directions that could be used in early GPS navigation-style devices, and struck a masterful bargain. “We called them up, and they gave us the technology for free,” said Kimbal. Musk merged the two databases together to get a rudimentary system up and running. Over time, Zip2’s engineers had to augment this initial data haul with more maps to cover areas outside of major metropolitan areas and to build custom turn-by-turn directions that would look good and work well on a home computer.

Replies (1)

  • @feld@friedcheese.us 2025-02-10 19:24

    @calcifer@hackers.town @shanselman@hachyderm.io and > While Musk had exceled as a self-taught coder, his skills weren’t nearly as polished as those of the new hires. 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. The engineers also brought a more refined working structure and realistic deadlines to the engineering group. This was a welcome change from Musk’s approach, which had been to set overly optimistic deadlines and then try to get engineers to work nonstop for days on end to meet the goals. “If you asked Elon how long it would take to do something, there was never anything in his mind that would take more than an hour,” Ambras said. “We came to interpret an hour as really taking a day or two and if Elon ever did say something would take a day, we allowed for a week or two weeks.” and > Employees at Zip2 would go home at night, come back, and find that Musk had changed their work without talking to them, and Musk’s confrontational style did more harm than good. “Yeah, we had some very good software engineers at Zip2, but I mean, I could code way better than them. And I’d just go in and fix their fucking code,” Musk said. “I would be frustrated waiting for their stuff, so I’m going to go and fix your code and now it runs five times faster, you idiot. There was one guy who wrote a quantum mechanics equation, a quantum probability on the board, and he got it wrong. I’m like, ‘How can you write that?’ Then I corrected it for him. He hated me after that. Eventually, I realized, Okay, I might have fixed that thing but now I’ve made the person unproductive. It just wasn’t a good way to go about things.” These specific excerpts are from the 2015 Elon Musk book by Ashlee Vance which Elon didn't want written/published

    Open ##2233472