3 ms·
Can someone explain to me what kind of software they were developing and what kind of problems they were facing? The post is very thin on details
by kramerger 3y ago
Can someone explain to me what kind of software they were developing and what kind of problems they were facing?
The post is very thin on details
- FirmwareBurner 3y agoHow many big companies do you know who give out public details to the press about the technical issues they are facing during development?
- kramerger 3y agoThe whole article is about "everyone have problem with this". What is "this"? Why is it so problematic?? Is it realy an invalid question? Besides, I'm sure someone on HN has inside info on this.
- FirmwareBurner 3y ago"this" being "the software" Carriad is working on and has to ship to VW companies. Why would Carriad give more details about the issues their are facing with their SW? Maybe those issues aren't technical but are just masking an organizational shit show, which given my experience with large SW projects in Germany would be mi first guess, but either way, it's not like Carriad has any incentive to hang their dirty laundry in public so that everyone can see how much they suck at whatever their doing so I don't get why you're expecting them to when there's no positive benefits for them to do so but only negatives.
- madduci 3y agoMy vote goes for Scrum and micromanaging. I wonder what are 2000 people needed for, in such a project.
- thephyber 3y agoAs of 4 years ago, the VW Group strategy was to have multiple competing OSes (close to one per brand). Around 2019, VW Group changed their strategy to unify software for all brands and platforms under the same car OS and bring more of the module/vendor code in-house. This is partially useful as the company-wide goal is to convert most of the fleet to electric, but also to change the revenue model somewhat (increase subscriptions and ICE pay features). Some background: https://arstechnica.com/cars/2019/09/volkswagen-audi-porsche-vw-group-plans-one-os-to-rule-them-all/amp/ https://arstechnica.com/cars/2019/09/volkswagen-audi-porsche...
- CBarkleyU 3y agoCARIAD is suffering from being born out of two forced merging strategies (Carmeq into CarSW into Cariad) while having two silent killers waiting for the perfect moment to snap (Audi, Porsche ousting Diess). It's sad. Volkswagen should've just stuck with having a better in house dev team for it's Volkswagen brand while leaving Audi and Porsche do their own thing. VW just tried to do too many things at once for too many parties. Obviously there's no "one thing" that they were struggling with, it's a company with 6000 employees trying to juggle several VW brands needs, sometimes against their wish. They're paying good money tho (Germany money, not silicon valley money)
- kramerger 3y agoSo you think internal politics among brands is what has caused most issues? I can actually see that happening. But if that's the case some Audi and Prosche managers should also get the boot for not getting this collaboration to work
- CBarkleyU 3y ago> But if that's the case some Audi and Prosche managers should also get the boot for not getting this collaboration to work Seeing how they practically ousted the last CEO and installed the new CEO, I'm not sure how that's gonna roll. In the end, CARIAD didnt deliver at all and it's hard to argue in favour of them.