Software leadership team fired

The vast majority of conspiracy theories are absolutely counter to Occum’s Razor.
The vast majority of Conspiracy Theories are exactly that. Theories and not things that are actually happening.

The few that turn out to have any basis in reality at all doesn't mean the next wackjob theory has any more chance of being true.
 
The vast majority of Conspiracy Theories are exactly that. Theories and not things that are actually happening.

The few that turn out to have any basis in reality at all doesn't mean the next wackjob theory has any more chance of being true.
A lot of fun to discuss over a couple of beers but not to use in deciding health, investing and voting decisions.
 
For the record, I’m happy with the car - but the whole purchase/delivery process was sketchy.
mine wasn't sketchy, but I'm never super confident when the new owner seems more knowledgeable about the vehicle than the delivery person.

but yeah, the whole filling out and DocuSign-ing all the paperwork online via emails from people one doesn't know is an odd experience vs. doing it all in person under one roof. with or without the undercoating. but then I'm old. ;)
 
This isn't a matter of belief. It's application of the principle. It's that "simple".
If the principle of Occum's Razor (quite famiilar with it) is going to be applied, as suggested, "you got unlucky" is a more simple answer than Lucid conspired or didn't care.

Continued discussion doesn't contribute to this thread; not software related.
Go with whatever you choose to believe regarding your car. It's your car.
Lucid has a well earned and now famous history of selling cars with known tech issues. It’s what they do.

if they’d told him the drive unit needed replaced, he wouldn’t have bought it. They did the same to me with my first Air.
 
Lucid has a well earned and now famous history of selling cars with known tech issues. It’s what they do.

if they’d told him the drive unit needed replaced, he wouldn’t have bought it. They did the same to me with my first Air.
That takes more planning, coordination and skill than delivering a working car. So I doubt it.
 
Agree, the fact that someone said "it's good enough, let's go" is mind boggling with how poor this vehicle is from an experience of living with it.
I regret every day for jumping in to the ownership / lease of this vehicle , the price I paid to be an "Alpha" software tester is not worth the frustration of daily new issues. Today it was this one:

View attachment 35882
You have my sympathies. There's a lot of talk here about how nice all the Lucid employees are. But ultimately the organization made the decision to sell obviously defective cars to the people purchasing last year, and damn the consequences. While some of us went into that eyes-wide-open, and many here have repeatedly posted "caveat emptor", it's nevertheless not a good brand reputation to establish Lucid as a company that will screw some customers and then try to clean up the mess afterward. The fact that there's some truly great engineering in the Gravity and that many consider the frustrations to be worth it doesn't wash away the stain of how they decided to treat some of their customers. I still think the Gravity is a really great SUV, but I took the $1K hit and bailed out of my pre-order when it was ready for delivery last month. I'm going to wait until the summer, or perhaps for the 2027 models, and think about buying when they've cleaned up the problems that are plaguing the vehicle.
 
That takes more planning, coordination and skill than delivering a working car. So I doubt it.
I'm not going to theorize what happening in that particular case. But it's entirely possible to believe that the organization made the decision to ship as many cars as possible, perhaps because they worried about Wall Street's reaction to further delay. Once they've made that decision in aggregate, knowing full well that the service team would quickly see a lot of the early deliveries come back, then what's one more in the queue? Your thought process is also reasonable, but one then has to ask why they didn't apply that thought to all of the deliveries they were making.
 
Lucid has a well earned and now famous history of selling cars with known tech issues. It’s what they do.

if they’d told him the drive unit needed replaced, he wouldn’t have bought it. They did the same to me with my first Air.
They planned on making you miserable? Okay. Seems likely.
 
You have my sympathies. There's a lot of talk here about how nice all the Lucid employees are. But ultimately the organization made the decision to sell obviously defective cars to the people purchasing last year, and damn the consequences. While some of us went into that eyes-wide-open, and many here have repeatedly posted "caveat emptor", it's nevertheless not a good brand reputation to establish Lucid as a company that will screw some customers and then try to clean up the mess afterward. The fact that there's some truly great engineering in the Gravity and that many consider the frustrations to be worth it doesn't wash away the stain of how they decided to treat some of their customers. I still think the Gravity is a really great SUV, but I took the $1K hit and bailed out of my pre-order when it was ready for delivery last month. I'm going to wait until the summer, or perhaps for the 2027 models, and think about buying when they've cleaned up the problems that are plaguing the vehicle.

I’m right there with you, and I’ve officially reached my breaking point. As a Dream Edition owner, I’ve moved past 'frustrated' and gone straight to legal action. I have hired a Lemon Law attorney to fight this.

It is absolutely unacceptable that Lucid sold us a vehicle north of $130k only for us to live in daily fear of the next software defect. We aren’t talking about minor 'early adopter' quirks; we are talking about the absence of standard EV technology found in cars a third of the price.

Every day is a gamble. Will my phone actually connect for a business call via Bluetooth? Will the key fob work today? Will my backup camera actually turn on as I try to navigate a tight city garage, or will I be blinded by a random error code that may or may not be critical? To have 'table stakes' features like Phone as a Key or CarPlay still missing or unreliable on this platform is a fundamental failure of the product promise. I shouldn't feel a surge of anxiety every time I walk up to this machine.

I agree that the raw engineering is impressive in a vacuum, but that engineering is meaningless if the user experience is broken. Lucid chose to ship these cars knowing they weren’t ready, effectively turning their most loyal customers into unpaid beta testers. I’m not waiting until 2027 for them to 'clean it up' ... I’m holding them accountable now.
 
FWIW, I think think this is refreshing honesty, and the right first move. In an engineering organization, leadership is responsible for setting the culture, the quality standards, and the development processes. These should all protect against a few bad engineers because there are layers of review, validation, and tracking before bad software reaches production. That didn't happen -- and regardless of why, leadership is accountable.

When you have a failure like this, you replace the leadership. It's the new team's responsibility to fix the process, and then determine if the quality problems are starting at a lower level with the engineers. This is exactly right, and the only thing I can fault Lucid for is not doing it sooner. I assume the problem was "we're 90% there, we can just get to launch" not realizing the remaining 10% would take another 90% of the time without first fixing the failing engineering practices.

It's hard for me to say, but a lot of the glitches I've been seeing scream "vibe coding" to me -- using code assistants to write functionality without understanding how it works or reviewing it properly, and creating layer upon layer of technical debt. I wonder if someone in leadership jumped on the AI assistant bandwagon early on without understanding how to make these tools effective, and it bit them in the end. All of the display and synchronization glitches really push me toward this belief, because it's what I'm most used to seeing in otherwise impressive-looking genAI-assisted development.
 
FWIW, I think think this is refreshing honesty, and the right first move. In an engineering organization, leadership is responsible for setting the culture, the quality standards, and the development processes. These should all protect against a few bad engineers because there are layers of review, validation, and tracking before bad software reaches production. That didn't happen -- and regardless of why, leadership is accountable.

When you have a failure like this, you replace the leadership. It's the new team's responsibility to fix the process, and then determine if the quality problems are starting at a lower level with the engineers. This is exactly right, and the only thing I can fault Lucid for is not doing it sooner. I assume the problem was "we're 90% there, we can just get to launch" not realizing the remaining 10% would take another 90% of the time without first fixing the failing engineering practices.

It's hard for me to say, but a lot of the glitches I've been seeing scream "vibe coding" to me -- using code assistants to write functionality without understanding how it works or reviewing it properly, and creating layer upon layer of technical debt. I wonder if someone in leadership jumped on the AI assistant bandwagon early on without understanding how to make these tools effective, and it bit them in the end. All of the display and synchronization glitches really push me toward this belief, because it's what I'm most used to seeing in otherwise impressive-looking genAI-assisted development.
Which is a shame too, sure the Air software isn’t exactly modern, but it does work significantly better than the gravity. I still can’t believe the screens don’t dim with headlights I mean that’s just absurd-but- it doesn’t have the game breaking bugs like the Gravity does. Something went wrong, obviously, with the Gravity, and poor decisions were made. We will probably never know the whole story.

I still insist the EE video take on software is overblown. The frunk is a fundamentally bad design that still isn’t fixed, but his issues with the profile switching is a pretty fringe thing really.The change door complaint was lame too. It’s fine.

When the new car is worse than the old car, something went wrong. The reason I suspect it’s “deliver now, fix later” at all costs is because these desperation for sales. It’s my background, I literally own a sales network. The pressure on people towards the ends of a tight goal, especially when owned by investors, is in unbelievable. Of course they delivered defective cars, to not do so would be career ending. Who made that call, we won’t know.
 
It's hard for me to say, but a lot of the glitches I've been seeing scream "vibe coding" to me -- using code assistants to write functionality without understanding how it works or reviewing it properly, and creating layer upon layer of technical debt. I wonder if someone in leadership jumped on the AI assistant bandwagon early on without understanding how to make these tools effective, and it bit them in the end. All of the display and synchronization glitches really push me toward this belief, because it's what I'm most used to seeing in otherwise impressive-looking genAI-assisted development.
You don't need AI to write bad code. You just need unexperienced software engineers and lack of a workflow that ensures quality.
 
There has got to be a way to ban people or put a temporary hold on some accounts if they keep repeating the same things everywhere. Every thread always end with a couple people hijacking it and almost always ruminating the same thing over and over. Please mods do something about this @borski , @Adnillien, @joec
 
There has got to be a way to ban people or put a temporary hold on some accounts if they keep repeating the same things everywhere. Every thread always end with a couple people hijacking it and almost always ruminating the same thing over and over. Please mods do something about this @borski , @Adnillien, @joec
This is a thread about terminations as a result of bad software and QA. It’s gonna have people in it, myself included, that have experience those issues.
 
This is a thread about terminations as a result of bad software and QA. It’s gonna have people in it, myself included, that have experience those issues.
Yes. And you’ve made your point many times over.

No one disagrees that you had a bad experience. No one disagrees Lucid is responsible.

But you are attempting to assign intent, which can’t possibly be proven. And when confronted with that simple reality, you continue to argue as if you can. It does get old, dude.

Let’s just agree that you can believe whatever you like. And we can continue to doubt what you believe?
 
Yes. And you’ve made your point many times over.

No one disagrees that you had a bad experience. No one disagrees Lucid is responsible.

But you are attempting to assign intent, which can’t possibly be proven. And when confronted with that simple reality, you continue to argue as if you can. It does get old, dude.

Let’s just agree that you can believe whatever you like. And we can continue to doubt what you believe?
So many pearls being clutched.
 
So many pearls being clutched.

See. Here’s the thing. I’m trying to be nice. And you’re trying to stir the pot. We have no use for that here. We’re a community. We’re here to help each other out.

If you can’t handle other people disagreeing with you politely and without having to be snarky about it, we’re going to have a problem.
 
There has got to be a way to ban people or put a temporary hold on some accounts if they keep repeating the same things everywhere. Every thread always end with a couple people hijacking it and almost always ruminating the same thing over and over. Please mods do something about this @borski , @Adnillien, @joec
You may already know this, but just in case; in addition to your post, you can also contact mods via direct message to provide them with additional information and better enable them to respond to your request.
 
Back
Top