Here's the specific timestamp of the incident you mentioned in case you wanted to actually see it: https://youtu.be/aqsiWCLJ1ms?t=1190
The car wanted to move through the intersection on a green left turn arrow. I've seen a lot of human drivers do the same. In any case, its fixed now and never was part of any public release.
The video didn't end there, it was near the middle. What you're referring to is a regression specifically with the HW3 model S that failed to recognize one of the red lights. Now I'm sure that sounds like a huge deal, but here's the thing...
This was a demo of a very early alpha release of FSD 12 (current public release 11.4.7) representing a completely new and more efficient method of utilizing the neural network for driving and has already been fixed. It is not released to anyone outside of a select few Tesla employees. Other than that it performed flawlessly for over 40 minutes in a live demo.
oh god i felt this one. Devs too busy, incompetent or just plain lazy to figure out why their code is so slow, so just have ops throw more CPU and memory at it to brute force performance. Then ops gets to try to explain to management why we are spending $500k per month to AWS to support 50 concurrent users.
not entirely. It makes it easy to filter out the kind of applicants that would put that on their resume. Very useful for hiring managers. Saves lots of time.
These textbooks are trash and written by morons. When I was in college one of the required books said very clearly that sleep and hibernate are exactly the same thing. It said that both suspended to RAM and hibernate was just some lower power version of sleep. It was even a question on an exam that I got wrong for some reason. I argued with the professor about it and proved to him thats not the case by taking one of the lab computers, hibernating it, physically taking the ram out and swapping it with another computer and resuming into the same state on power on. He said “Well thats what it says in the textbook so I have to mark it wrong”
It really highlights that there are probably a lot of other inaccuracies that I didn’t notice. This is the standard of education nowadays.
I had bought a new Samsung TV from best buy and after getting it home and setting it up, I noticed that any time there was high/low contrast content moving across the screen, the image would just smear across. This made a lot of content completely unwatchable. In LCDs this is usually a result of horrendously bad response time but this was so bad that something seemed clearly wrong/malfunctioning with the unit, so I called samsung for warranty repair.
Over the next few months I had a tech come out to replace the main board on the TV, but it still had the same problem. I booked another repair appointment. The same tech came to my house a few weeks after that and replaced the entire screen. Still the same problem. There was a thread that I found by this time on AVSForum of people with the same TV all complaining of the same issue.
At this point, Samsung's official response to me was "That's just how the TV is". I was really not happy about the idea of keeping the TV since I was outside the return period, so they gave me a phone number to call with a case number to escalate or hopefully resolve the issue. Its wild that they would ever even sell a TV like this.
Here's where it gets bad:
The next day I call the number around 10AM. I sit on hold for 7 hours, then at 5PM there is a message "Our office is now closed, goodbye" then it hangs up on me. No voicemail, no callback options, nothing. There is no option to email this department, they will only take phone calls.
The day after I call the number a little earlier, around 9 AM. This time I sit on hold for 8 hours, then again there is a message at 5PM that they are now closed and hang up on me.
I wait 2 days and call back around 9AM again. at 4:45 PM I get in touch with a human, but they aren't able to find any record of my case number and can't help me. They're about to close anyway, so I should just call back tomorrow. They hang up.
The next business day I got up at 7AM and called immediately when they opened, sat on hold for 8 hours and demanded to speak to someone who could actually help me. I sat on hold for another hour and eventually spoke to a manager who miraculously found my case number and acknowledged receipt that I called.
Samsung sent a company to come pick up the TV and gave me my money back about 2 months after that call. I had to spend 4 entire work days on hold with them to get them to acknowledge and take back their TV that was effectively useless garbage. I replaced it with a Sony and have been 100% happy ever since, its been working for several years now.
There was an issue in my neighborhood where an outage was reported that lasted months, only problem was that this was completely in error and there was no outage. Normally this isn't an issue but Xfinity's big-brain move is if there's an outage detected in your area, you are 100% unable to get in touch with anyone. Not by phone, chat, email, or anything. As soon as you give your service address it says "An agent will not be able to help you. Goodbye" then hangs up on you or closes the chat.
During this time my modem died and I had to get and activate a new one. I had to look up a fake address outside of the "outage" and give them a fake number to talk to an actual human. When I explained the situation and gave them my actual address, the agent started the process of getting me off the phone because there was nothing she could do. Eventually after pleading they were able to activate my new modem in about a minute.
This whole process took over a day and I lost a whole day of work because of it. They gave me a $10 credit on my bill to say sorry.
https://www.thedrive.com/article/21456/the-dangerous-difference-between-electrek-journalism-and-truth