Facebook. In the Gravity group, he replied to someone's post.where is this post from?
I hear you, but just doing what they were doing was clearly not working. And as others have said they couldn’t ignore things any longer, EE video or otherwise. Sometimes you need to decide who your best is, give them the ball and then figure out how you support/ backfill. I also suspect the drive unit failures are taking a different type of bandwidth: root cause analysis, five whys, etc, while software probably needs ruthless re-prioritization: these are the non-negotiable, shelve the other stuff. So as long as it’s something he’s ready to take on I’m ok with it. While hiring like hell in parallel, obviously- this isn’t scalable.I like Emad Dlala, but given that some Gravity drive units have already failed, I'm not sure putting more on this plate -- especially as heaping a serving of trouble as the UI software -- is a good idea. It strikes me as more a symptom of an organization that is running short on the talent it needs than an organization that has found the path to a solution.
I do hope I'm wrong.
I hear you, but just doing what they were doing was clearly not working. And as others have said they couldn’t ignore things any longer, EE video or otherwise. Sometimes you need to decide who your best is, give them the ball and then figure out how you support/ backfill. I also suspect the drive unit failures are taking a different type of bandwidth: root cause analysis, five whys, etc, while software probably needs ruthless re-prioritization: these are the non-negotiable, shelve the other stuff. So as long as it’s something he’s ready to take on I’m ok with it. While hiring like hell in parallel, obviously- this isn’t scalable.
If they don’t they have real issues at the board level. Which isn’t out of the question, but given Rawlinson‘s departure that seems less likely (though recognizing and constructively addressing an issue are completely unrelated in my experience, so maybe that’s wishful thinking).I'm not sure Lucid understands the approach they're taking isn't scalable.
But it’s a beautiful Saturday morning, what the hell else we gotta do?Meanwhile, probably best to refrain from speculation and armchair-ceo-ing the crap out of this thread.
I’ve got a software engineering background and was kinda thinking about this too, my thought was wondering if they’re moving towards integration with uber/nuro for the autonomous stuff? Maybe trying to prepare entry points for other systems or starting to work with additional hardware? Integrations can be a bi-atch! Then again, there’s probably enough variances in hardware components to keep the devs on their toes as it is(Putting on my second guessing cap on for a brief moment)
I wonder, since they are programming in Android auto - maybe the software platform does not handle all the complexity of the Lucid platform? Maybe they need to develop software apart from Android to use if that is even possible. The reason I say this is the early days of JAVA (had to inject C/C++ to speed up functions) or scripting languanges that do a certain function really well but falls flat doing other tasks. Just thinking out loud. I am sure someone will be offended. Therefore, correcting myself - The general software randomness is due to just squashing the bugs within the current software stack. Most likely the later and non of the initial 'evil' thoughts. (just provoking thought...)
Meanwhile, probably best to refrain from speculation and armchair-ceo-ing the crap out of this thread. That's probably too much to ask.
...and internal org strugglesthere's certainly no reason to own the stock based on its current financials and product launch stumbles.
...and internal org struggles
I was the liason between software engineering and marketing at Cisco. Yeah, it is challenging for sure! It a path every software development group must go though - rapid software development is never fast enough. Patience.I’ve got a software engineering background and was kinda thinking about this too, my thought was wondering if they’re moving towards integration with uber/nuro for the autonomous stuff? Maybe trying to prepare entry points for other systems or starting to work with additional hardware? Integrations can be a bi-atch! Then again, there’s probably enough variances in hardware components to keep the devs on their toes as it is
I was the liason between software engineering and marketing at Cisco. Yeah, it is challenging for sure! It a path every software development group must go though - rapid software development is never fast enough. Patience.
To be clear: this would be fine. If someone has actually had significant experience as a CEO or COO or similar of a major public company, especially if in tech or automotive, by all means - speculate! In fact, I'd encourage it.But let someone who knows something about organization design and effectiveness speculate on that front