Forgot your password?
typodupeerror

Comment Re:Elon is a contributing factor (Score 1) 105

The idea was never absurdly stupid. It was basically conceived right alongside modern rocketry. The problem has always been getting the bean-counters on board enough to take the risk to get it done. That was one of the things that got Musk the credit he initially got for SpaceX. He actually did put it on the line to actually allow this to be developed beyond one-off experiments. But, that's not because no one thought it could be done. Lots of people thought it could be done, there just wasn't the will to go all the way.

Comment Re:Economics of Starlink (Score 1) 105

Even with more launch capacity, it doesn't seem like they'll get remotely close to ground bandwidth, so you're right about it being hilariously uncompetitive when ground alternatives exist. A single optical fiber in deployment can typically carry around 30 Tbps. Experimental testing has gone up to 400+ Tbps. The laser link between Starlink sats is like 100 Gbs. So 300X slower than real world throughput on a single fiber. Even a really small fiber optic cable has about a dozen wires. Typically paired though, so we start with just a factor of 6. So that's 1800X faster than the Starlink connection for a super-basic fiber optic cable. But they can go up to hundreds of pairs. So, it's pretty easy to get a fiber deployment that's 30,000X faster than a Starlink to Starlink connection. Of course, then you look at the fact that there are only about 11K Starlink satellites up there and that they need line of sight for communication and consider the useful range of their communication and that data needs to basically travel through a relay network from satellite to satellite, that seriously restricts their use as a backbone. As it stands, Starlink mostly uses ground infrastructure for a data backbone (data down to ground station, through fiber, then back up from another ground station) despite the satellite to satellite links.

Comment Re: Economics of Starlink (Score 1) 105

I believe the story you're talking about was one of the stories in I, Robot. The robots have basically don't believe that humans created them and have their own religion centered on maintaining the integrity of the concentrated beam back to Earth. It is worth noting though that they are still bound by the three laws, but the structure of the three laws means that they still confine the humans in a radiation shelter during a solar storm. Basically, they still obey orders, it's just that the first law (not harming humans, even through inaction) overrides the second law (obedience to humans). After their confinement, the troubleshooters note that the robots kept the beam close to perfect through the storm. In then end, they basically conclude that if it isn't broken, don't fix it.

Comment Re:I think this amazing... (Score 1) 105

It's not flying cars exactly, but I think even the most skeptical critics were impressed by the car demo.

Not any more than by any cold-gas thruster demo or hydrogen peroxide based rocket belt from the fifties. I mean, look at the Williams Wasp X-jet from fifty years ago. Ignore the nonsense at the start of the video about how it is "mysteriously" no longer in use or development. That type of technology has been in continuous development, it has just always been niche. Musk was a toddler when this was developed and his Tesla demo was frankly less impressive than that, neat though it may have been.

As for it making short flights possible in the future, you have to understand that the tank for the cold gas thrusters is an energy storage device. It's made to be refilled by built in compressors in the car, but you have to look at the actual amounts of energy we're talking about here. The tank effectively stores around 20 kWh, and that takes about 3X as much energy to actually fill (200% loss). So, basically you can have one pre-stored hop, then use pretty much all the charge in your battery to store up for one more. This demo quite simply was not a stepping stone towards anything. This is just Musk getting his engineers to cover some wild, ridiculous claim he previously made about the next roadster.

Comment Re:Nice! (Score 1) 105

Then you need to educate yourself a bit on reasons to dislike Musk. I was quite enthusiastic for him early on, but more and more red flags kept popping up. The first big one was all the stories that I kept hearing about him arbitrarily firing employees. Some engineer disagrees with him or says something he doesn't like - fired on the spot. The more specifics come up, the worse it seems. For example, his assistant asks to actually take some of her vacation time, so he uses that to "prove" he doesn't need her and fires her. There was the whole "pedo guy" thing. I actually even sort of supported him in that, or at least pointed out that the other guy appeared to be an asshole too. Then of course there were all the lies and false promises and rigged demos, etc. And so it went, on and on, more and more details coming out about the man revealed him as an extremely problematic human being. By the time he ever actually revealed an actual political alignment, it was past the point where I was completely fed up with him. I will say, I wasn't particularly surprised by his political alignment at that point.

Comment Re: Nice! (Score 1) 105

I get your argument but as for "People who want to toss him in jail or take over his companies simply because they don't like him would be cutting off the nose to spite the face.", there are some considerations there. One of them is the "simply because they don't like him..." That mischaracterizes many people's dislike of him as purely irrational. Sure there may be some who don't have rational reasons, but there are plenty who dislike him for pretty rational reasons, up to and including the fact that he seems to have committed numerous crimes ranging from immigration fraud, to securities fraud to crypto racketeering, to large-scale cybercrimes at DOGE, to election interference and bribery, to union busting, to Logan and Hatch act violations, to embezzlement, to whatever he wanted to do on Little St. James island on the wildest party night. Those are just the things that many people think he should be criminally investigated for. The list of things that people simply don't like him for is much larger. Then there's the list of things that don't necessarily have to do with disliking him, but that seem to be major, major red flags as far as his business dealings and business ideas go.

Also, as far as cutting our nose off, it's pretty hard to say what we would lose if we lost Elon Musk at this point. I mean, what has he actually done lately? SpaceX always worked mainly because of people like Tom Mueller, Hans Koenigsmann, Gwynne Shotwell, etc. and then the people they later brought on and trained up. With the business structure in place, Musk doesn't seem to actually contribute much. I mean the guy regularly has nothing to do with the company for weeks or months at a time while he's running off doing something else like trying to move Twitters servers himself by hand with rented moving trucks. How vital can he be? Not to mention that, while he's there, he's a pretty well documented reason for the departure of numerous brilliant people because, whatever excuses some might make for "demon mode" he's an abusive, unreasonable boss.

Comment Re:Pluto is a planet (Score 1) 70

You guys do know that there's a process in motion right now to make this debate meaningless and redefine "planet" again? As it stands, the current definition of planet you're arguing over doesn't include any "exoplants". It's actually weird, solar-system centric definition that clearly has no future. They're looking to define clearing its own orbit as 10^23 kg.

Comment Re:From one dev manager to another (Score 1) 153

No actual disagreement with what you're saying there, but a few things about your example. A. You were dealing with at least one competent engineer and B. you're talking about mechanical engineering. We both agree that you need to hammer out the details with the client, but many clients looking for software to be developed are not engineers and frequently not even all that technical plus the ease of rolling out a mockup or prototype is generally a lot easier in a pure software environment. So sometimes hammering out the details can involve a mockup as a version of the specification for them to pore over. Especially for UI and workflow elements. Beyond that, sometimes dealing directly with the engineers whose requirement it is can be a bit of a luxury. Often you're dealing with one or more layers of middlemen. Worst cases can include your salespeople working out the requirement with their salespeople. If you lose the battle to have at least a constructive conversation over their heads, you're generally stuck with the sure and certain knowledge that there's some fundamental misunderstanding in the middle.

So, that's really the comparison I'm making here. In the traditional paradigm, you ideally have competent engineers/developers or even technically inclined end users who can work everything out. This new paradigm threatens to have the "developer" become the one who has no idea about what has been asked for, what it would really be used for, how to ask the right questions to improve the requirements documents, etc. They just become a middleman who feeds that into the AI.

Comment Re:From one dev manager to another (Score 1) 153

Anyone who has enough development experience and dealt with the client facing side of it knows that the client never has a clue about the requirements. An important part of the job is, in polite terms, telling them how stupid their original set of requirements is and hammering out with them exactly what they actually need (that or just ignoring them, intuiting all of that, then just making the specific changes they want after you hand them a prototype). Basically, what we seem to be talking about here is turning the developers/engineers into the clueless clients who have no idea what the requirements should actually be anyway, and using the AI as a developer that just takes the requirements at face value.

Comment Re:From one dev manager to another (Score 4, Insightful) 153

Your process for interviewing should not change. You need engineers that can think well to judge the output of an LLM well.

Quite right. The logic the manager from the article is presenting is incomprehensible. They're arguing what? That you don't need coding problems in interviews because an AI can do them instead. Classically, they have been stock problems that are pretty much just mild variations of standard stuff from textbooks. So if you don't need to bother with them now because AI can do them, then you never should have needed to bother with them because the problems had already been done before, thousands of times, and written down. What does this guy think, that the coding problems in interviews are vital new developments in computer science or something? Now, some companies do actually present those as problems just to see how the interviewee approaches them, and there are also some stories about unethical companies that have used long-form interviews as a way to get programming piecework done for free by suckers, but that's not what's being discussed here. The point is that we're talking about a basic way to make sure that interviewees actually understand the concepts themselves, not asking for the interviewee to demonstrate that they can accomplish some amazing task that no-one else on Earth could perform.

Slashdot Top Deals

Advertising may be described as the science of arresting the human intelligence long enough to get money from it.

Working...