“Mistakenly, we thought that by just introducing artificial intelligence and adjusting the design requirements that we had, that that would produce a high-quality product,” said Charles Poon, VP of vehicle hardware engineering, in a briefing this week with reporters.

top 100 comments

sorted by: hot top controversial new old
[–] 261 points 4 months ago (30 children)

So they fired the executives responsible, right?

  • source
  • hideshow 30 child comments
  • [–] 157 points 4 months ago (19 children)

    Lol. Probably got bonuses then celebrated for identifying the issue and fixing it.

  • source
  • parent
  • hideshow 19 child comments
  • [–] 33 points 4 months ago (3 children)

    *Underpaying someone else to fix it.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 4 months ago (2 children)

    trust me no, the follow up is often an overpay

  • source
  • parent
  • hideshow 2 child comments
  • [–] 23 points 4 months ago (13 children)

    Heh, a few weeks back a new project manager at my work held a meeting about an upcoming project, and half the team was able to say the timeline was workable, but the specifics the project manager laid out would lead to disaster, and we just had to adjust the strategy, but still have same time and same cost. We spelled out exactly what would go wrong and how, based on previous attempts to do it the way he said. It was scheduled to be a weeklong project, which would have been a fine timeline.

    He got stubborn, insisted that based on his research his approach was right, and while he would have us on standby in the unlikely event of a problem, he would largely outsource the project to a company that agreed with his plan.

    So the project started Monday, and based on past experience we expected to be called into action on Tuesday morning and have to hustle, or maybe Tuesday end of day and really get overworked to close it in time. So Friday comes along and we are shocked that it must be going ok since we hadn't heard anything. 4pm rolls around, the project manager calls us in a panic saying it's all gone nowhere, zero progress made, and he has escalated to make sure we take over and now we had to make the Monday morning deadline, or our asses are screwed. Everyone worked their asses off, a couple didn't sleep the whole weekend.

    So in a followup call, the project manager said "no one could have predicted it would go so badly", and then an email came out from executive team congratulating the project manager for making the project work despite challenging circumstances.

  • source
  • parent
  • hideshow 13 child comments
  • [–] 12 points 4 months ago (3 children)

    I would literally go "Nope, no going to happen, you deal with you making promises with estimates you yourself made up instead of listening to the experts".

    In fact, I've already done this in the past.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 4 points 4 months ago (1 child)

    This as a good example of how people fail upwards.

    If he had listened to us from the onset, this would have proceeded, he would have been maybe casually acknowledged for a solid enough job, business as usual even though the money in play was abnormally astronomical, leadership would have just taken this part of the business for granted.

    Because he didn't listen, he created a disaster. Because the disaster had just unimaginably large amounts of money attached with just stupid amounts more potential money in followup business, the executives were panicked. The ability to recover it on schedule suddenly they appreciated it, and he manages to bask in the spotlight.

    Ok, so what if we had left him out to dry? We probably would have been fired. He probably would have too, but declining to assist and risking millions of dollars of business screws you too.

    The upside? Well, this was noteworthy because this was the first time in many years I had to lose a weekend, so it's not super common. To the extent stuff like this happens more regularly, it usually isn't this bad and is more annoying but on normal business hours. This also happened close to review cycles, and was fantastic relevant information to hold over management so while I didn't get broad recognition, I did walk away with the second largest bonus of my career. Also the project manager learned the lesson and his standard game plan for this sort of thing is now consistent with what we said. He fails upward, but at least he's an ally for the foreseeable future.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 9 points 4 months ago* (last edited 4 months ago) (2 children)

    That would make me quit on the spot. No notice. No explanation. Just get up and leave and not say any word to anyone.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 9 points 4 months ago

    If you have concerns like that always express them in an email as well as verbally, not only is it good for covering your own ass if you weren't able to pull it out the fire (tbh I think you shouldn't have busted your ass to make it work), but its also going to make people less likely to claim that unearned credit for your heroic work if you do.

  • source
  • parent
  • [–] 2 points 4 months ago (2 children)

    I hope the team was paid a nice overtime fee. Otherwise they should have just let it fail.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 4 months ago (1 child)

    Well, salaried, so not 'overtime' per se, but at least I walked away with a bonus equivalent to about 4 months pay. Not solely due to that one incident, but that incident put things over the top.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 4 months ago

    Good for you.

    Here in Belgium, with salary contracts, there is still a calculated daily pay, IIRC it is monthly salary / 22.

    If I work on a non-work day, I get 150% of this for a Saturday or 200% of it for a Sunday or public holiday.

  • source
  • parent
  • [–] 1 point 4 months ago (1 child)

    sounds like a layoff is coming if they are doing this.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 4 months ago

    Well, it's complicated. Basically my team has done this sort of work for a long time, but for a different market segment. This is a new market segment, but with respect to our work it acts the same. However executives don't understand that, so they spun up another organization to deal. Further, the company that was supposed to do it instead of us had brand recognition in the market despite being terrible at the part of the work that we know how to do.

    So we weren't being replaced, we were seen as not relevant to this "new" market. That vendor wasn't going to touch our market with a thousand foot pole.

    What we seem to be settling into is for us to do it our usual way, then hand over to that revered company to finish it in a way to cash in on brand recognition and admittedly do things a bit more particular for that market after our usual jobs are done.

  • source
  • parent
  • [–] 60 points 4 months ago (5 children)

    Can we start replacing executives with AI? Big money savings there, and you don't even need a particularly good model

  • source
  • parent
  • hideshow 5 child comments
  • [–] 89 points 4 months ago (3 children)

    Seems like we’re entering the “find out” phase…

  • source
  • hideshow 3 child comments
  • [–] 3 points 4 months ago

    We definitely are in some ways, but I don't think this applies. Just the past month I've seen several articles about companies doing real work on scaling back AI use, which is good. But a bigger number are still fully invested and everyone who has any say about it have such an extreme AI psychosis that the companies, and possibly themselves, won't survive.

  • source
  • parent
  • [–] 67 points 4 months ago (4 children)

    According to Poon, some of the company’s most experienced personnel left before all of their accumulated knowledge could be fully transferred into Ford’s automated systems. That necessitated bringing back some of those employees to retrain those systems...

    See this, nothing was learned by these slop-shits. Their take away wasn't humans-with-experience > than slop-bots. It was, unfortunately, 'we didn't extract enough knowledge from the humans that helped build our company before tossing as many humans away as possible. Once we've extracted enough, we'll try again.'

    Fuck you poon and co.

  • source
  • hideshow 4 child comments
  • [–] 6 points 4 months ago (1 child)

    Let's hope the humans learned their lesson and won't teach the systems.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 6 points 4 months ago

    The point the grandparent comment is making is that there is no amount of teaching that will turn an LLM into a top engineer. The technology just isn't there yet, not until OpenAI replaces all their own engineers.

    🧐 1
  • source
  • parent
  • load more comments (1 reply)
    [–] 66 points 4 months ago (4 children)

    Hopefully those employees said, "Sure, I'll come back, but my salary requirement is 50% more than you were paying me."

  • source
  • hideshow 4 child comments
  • [–] 46 points 4 months ago

    I always thought it was a joke until it happened to friends of mine. Massive layoffs, they were experts in one specific technology, they came back as consultants for a few years with a doubled salary. They were fired again later, but with a lot more money so it was worth it.

  • source
  • parent
  • [–] 8 points 4 months ago (1 child)

    In the current job market, you know it was the other way round.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 22 points 4 months ago

    If the company proactively reaches back out to you, you have the upper hand, regardless of the general hiring atmosphere. It indicates that they don't want to take the time for someone else to ramp up on institutional knowledge they know you already possess.

  • source
  • parent
  • [–] 63 points 4 months ago (3 children)

    That’s such a dumb fucking quote. Imagine being a stockholder and reading that sentence spouted from someone at the helm of the company.

    Kick rocks, wet socks.

  • source
  • hideshow 3 child comments
  • [–] 2 points 4 months ago

    They'll never hear that though, they'll hear what the want to hear, both via the people at the company and their own brain filter. Then they might see this and other articles but that doesn't matter because they're so far down in the hole of AI psychosis.

  • source
  • parent
  • [–] 59 points 4 months ago (1 child)

    Mistakenly, we thought that by just introducing artificial intelligence and adjusting the design requirements that we had, that that would produce a high-quality product

    That's so low IQ, like saying "Mistakenly, we thought that by just introducing a lawn mower and adjust the landscaping requirements, that that would produce a high quality lawn."

  • source
  • hideshow 1 child comment
  • [–] 24 points 4 months ago*

    Exactly, it's incompetent managers making stupid decisions in the hope of looking good by reducing headcount. People see this and think aha, one more reason to hate AI, but blaming AI is like blaming a fork for not being a spoon.

  • source
  • parent
  • [–] 43 points 4 months ago (2 children)

    So the VP quit or was right fired, right? Right?

  • source
  • hideshow 2 child comments
  • [–] 38 points 4 months ago (6 children)

    I hope they had to double their previous salaries...

  • source
  • hideshow 6 child comments
  • [–] -4 points 4 months ago* (last edited 4 months ago) (5 children)

    I had they hope to previous thier double saliear

  • source
  • parent
  • hideshow 5 child comments
  • [–] 2 points 4 months ago (4 children)

    Durr regard made jokesers fucks it ip halwauthit

  • source
  • parent
  • hideshow 4 child comments
  • [–] -2 points 4 months ago (3 children)

    The joke is NOT I fucked up correcting myself editing it about it, the joke is that I care so much that I make this meta comment. That's the level of joke we're on

  • source
  • parent
  • hideshow 3 child comments
  • [–] 35 points 4 months ago (2 children)

    And they're going to fire Charles Poon for fucking this up, right?

  • source
  • hideshow 2 child comments
  • [–] 32 points 4 months ago (2 children)

    The Broligarch's are reading the wrong philosophers. If they read Polanyi they would know that you can't build a tacit knowledge system based on explicit knowledge. Its summed up in the pithy "we know more than we can tell". https://en.wikipedia.org/wiki/Polanyi%27s_paradox

  • source
  • hideshow 2 child comments
  • [–] 31 points 4 months ago
    • Yes sir I can fix those, I only charge 10.000 euros / hour.
  • source
  • [–] 29 points 4 months ago

    “would produce a high-quality product,”

    Ai couldn’t do it. Real engineers can. However C suite gonna rebute high quality in favour of service and product that fleeces the most of the buyer.

  • source
  • [–] 48 points 4 months ago (10 children)

    I've been using an LLM for programming for last 6mo and it needs constant babysitting. It's basically something that just does the most straightforward thing without consideration of nuance, maintainability or whether to actually split into a module. This is very much not surprising.

  • source
  • hideshow 10 child comments
  • [–] 13 points 4 months ago (4 children)

    Yeah, I use it for some programming tasks as well. I’m sick and tired of telling it that it did something wrong or simply omitted something, only to have it apologize and offer to fix its own mistakes.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 17 points 4 months ago (2 children)

    The major problem is that the work of an LLM has a massive number of hidden 'assumptions' that you need to be aware of. If you don't already have a good working knowledge of the task you wont have an intuition about those assumptions. It's annoying.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 4 months ago

    Yeah, and for those who don't know, the rationalization output of the LLM is just so pursuasive. It sounds quietly confident and rattles off things that sound like real details.

    People are believing the LLM output over actual human experts and the human experts have to expend non-trivial effort trying to disprove an LLM output before they can get on with the business of doing it right.

  • source
  • parent
  • [–] 3 points 4 months ago

    Yeah, like cards being the best thing ever on front-end. If I want a basic layout I put "avoid cards" usually because then it'll use them sparingly. But yeah, it's just autocomplete so it's always going to get the lowest common denominator code based on what it decided to look at.

    I'm now looking into finding something faster than GPT/Claude where I can ping pong prompt faster and get what I want. Whatever it writes first is just a first draft anyway.

  • source
  • parent
  • [–] 7 points 4 months ago

    You should be glad it's apologizing. On the occasions I've used it to try to actually write code for me it's had a tendency to blame me for its mistakes.

    It writes a function that gets stuck in an infinitely recursive loop that never exits, I point it out and it's all "Aha! You've fallen for a classic recursion trap!" What do you mean I've fallen for it?

    Between those experiences and seeing the hot garbage some of my coworkers vibe coded, it was enough for me to relegate LLMs purely to the "ask questions that you would have searched for on StackOverflow" role. And it frustrates me that search was made so impotent that it's not a real option to avoid the LLM entirely. The multiple answers and perspectives on SO were often really valuable.

  • source
  • parent
  • [–] 12 points 4 months ago* (1 child)

    The active dev I know who uses it daily says it drastically reduces the time he spends on routine tasks and sometimes comes up with novel approaches, but he definitely has to check everything. The problem is inexperienced or non-experienced people thinking it's a magic lamp you can rub and it poofs out an expert programmer.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 9 points 4 months ago (1 child)

    It's obnoxious enough to try to use for myself, sometimes useful but obnoxious to review the code and just constant screwups except for exceedingly boilerplate stuff or stuff that can take some sloppiness (e.g. LLM can make it easy to indicate some variables to get from argv and do the tedium of that plus help text plus man page edits and generally do that fine). Even if it doesn't screw up obviously, if the code is verbose, I know a screw up is lurking and just ditch it and do it myself.

    However, the real pain comes in as other people use it. Just today someone had an issue and normally they'd ask a developer for help and offer debug appropriate information and/or access. However, they "just had Claude do it, even used Opus 4.8 to make sure it's good" and it generated a very verbose report on the issue, why it went wrong, and the appropriate change to make it work. Very detailed and the explanation sounded quite reasonable. Problem was that it was horribly and absolutely wrong, a fiction of a rationalization over a bad code change. It made a change that happened to appear to work for him, but in reality it replaced a failure due to unrecognized data to silent corruption of the data in a facet the user specifically did not care about. Claude claimed it was correctly mapping the unrecognized data correctly, but it just made up a completely untethered conversion based on nothing. Now I could tell the explanation and code change was bullshit at a glance, but it became an argument because the user wouldn't give me actionable debug details because "he already had Claude fix it". I had to keep trying to find holes in the Claude rationalization that the user would also recognize, and he sided with Claude four times until the fifth problem in Claude's explanation finally stuck (it asserted that the problem was due to running a specific outdated version of a specific software, problem being that specific version never even existed, and the minimum "good" version was 10 years old and the version the user was running was about a month old).

    I don't understand how people get this far and still don't understand that AI is much better at sounding plausible than being correct.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 4 months ago

    100%, when you have a complex domain and business logic that already has a bunch of legacy spaghetti it'll just make shit up.

    Normally for bug fixes I ask the LLM to find it and then I tell it how to fix the bug which is a lot more hands and actually fixes the issue more often.

  • source
  • parent
  • [–] 21 points 4 months ago (1 child)

    just goes to show, mid-level lackeys will do anything for Poon

  • source
  • hideshow 1 child comment
  • [–] 20 points 4 months ago

    I hope they negotiated their new salary very strongly

  • source
  • [–] 20 points 4 months ago

    VP should be fired.

  • source
  • [–] 19 points 4 months ago

    Very normal story at this point. Managers incompetently think AI will magically replace employees, they lay off employees, it doesn't work, they rehire the employees.

  • source
  • [–] 18 points 4 months ago

    I assume someone got a big bonus for that decision and now someone (maybe even the same person) gets a big bonus for the decision to rehire.

  • source
  • [–] 36 points 4 months ago

    AI is a tool not an employee.

  • source
  • [–] 15 points 4 months ago

    In addition, the automaker underestimated the value of the institutional knowledge accumulated by its more veteran engineers who had worked through multiple vehicle-development cycles. And this combination of phenomena led to a drop in quality in Ford’s vehicles.

  • source
  • [–] 15 points 4 months ago

    "Mistakenly"? More like delusionally. The shortcomings of current AI systems are hardly a secret. Anyone who spent a few minutes getting informed would be aware of those.

  • source
  • [–] 13 points 4 months ago (3 children)

    Years ago I worked at an ISP tgat went through a merger. They decided they were going to outsource customer service to another company.

    We all got nice severances and 3 months prior notice where we basically didn't work because all calls were being routed to the new call center and we were just backup. What a great 3 months. We had card tourneys, spun up the companies old game servers and ran minecraft (alpha) on them, lots of fun.

    Get laid off, fast forward a year and the outsource company has taken an 86% approval ratimg down to the low 30s.

    They hired a lot of us back to completely rebuild the service department. I was tier 1 and got a 76% raise. I imagine others got better.

  • source
  • hideshow 3 child comments
  • [–] 20 points 4 months ago* (2 children)

    I bet the executives who made the decision gave themselves a bonus and are still working there despite the monumental blunder.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 4 months ago

    There can be value in having learned things the hard way. The decisions I made that resulted in melted piles of scrap really seared themselves into my memory, and help me make better decisions around those systems going forward.

    Unfortunately, our corporate systems aren't great at distinguishing people who gained valuable lessons from people who don't recognize they screwed up.

  • source
  • parent
  • [–] 11 points 4 months ago (7 children)

    Hoooo boy, make sure you never buy a Ford again.

  • source
  • hideshow 7 child comments
  • [–] 17 points 4 months ago (5 children)
  • [–] 2 points 4 months ago (2 children)

    Even Mercedes does it but mine had no leaks at 240k km.

    They'll shave weight in the stupidest places to meet emissions.

  • source
  • parent
  • hideshow 2 child comments
  • load more comments
    view more: next ›
    9 comments in c/technology@lemmy.world view that post