Good read. Sad ending that all that work ended up nowhere.
Good read. Sad ending that all that work ended up nowhere.
NEW feature: As you drive down the road, Ford cars will automatically take over and drive you to the nearest sponsor location. Hungry? It will take over and swerve into the nearest KFC drive-thru. Next stop, CVS pharmacy, then Office Depot.
Disclaimer: Disabling AutoAd feature requires monthly subscription.
When this whole ‘training’ trend started a few years ago, there were companies offering image and video labelling services.
It turned out they were mostly sweatshops in low-income countries, where people sat in front of monitors and just dragged boumding boxes around sections of images and picked from an icon menu. Here’s a car, here’s a person, here’s an apple. That sort of thing. You didn’t even need to know how to read or write.
Of course, the quality was questionable, so they needed a second layer of supervisors verifying the choices. But even with that, the cost was way lower than having an engineer or QA person do it. IIRC, there was a bit of hue and cry when stories came out of big tech companies supporting sweatshop conditions.
Sounds like it’s still ongoing.
NEW, automated children’s bicycle. Guaranteed to teach the little tyke how to ride! *
I’ve always kept a strict separation between work and personal projects, including a personal laptop, accounts, and yes, paying for AI services. For a while, a few years ago, while commuting on the company shuttle, I even had my own MiFi cell access point and a laptop battery booster so I could work on my own projects on the bus and not be accused of using company resources.
Most employment contracts spell out that anything you create using company resources is the property of the company. Legally, they own everything that passes though their computers, software, and networks.
Also, many corporations run system monitoring services on their laptops and MDM mobile data management on mobile phones (for example JAMF on Apple devices). These monitor things like file access, copying, communications, and web access. This data is sent to central servers for processing and looking for anomalies based on pre-set rules. This might sound tin-foily, but it’s mandated by legal in a lot of companies, including small and medium sized ones.
If you want to use non-company data to do AI work, or develop a service or idea on your own, or even keep your text messages and email private, you’ll want to use your own equipment, accounts, and services.
Edit: also, if you get laid-off or fired, you’ll want to have a decent personal rig so you can continue working on your own projects while looking for work. Even if working on a novel on the side, suggest keeping everything off company systems.
IRL, arms manufacturers claim they’re not culpable when their products are used to blow up civilians. They point at the people making decisions to drop the bombs as the ones responsible, not them.
This legislature tries to get ahead of that argument, by putting reponsibility for downstream harm on the manufacturers instead of their corporate or government customers. Even if the manufacturer moves their munitions plants elsewhere, they’re still responsible for the impact if it harms California residents. So the alternative isn’t to move your company out of state. It’s to stop offering your products in one of the largest economies in the world.
The intent is to make manufacturers stop and put up more guardrails in place instead of blasting ahead, damn the consequences, then going, oops 🤷🏻♂️
There will be intense lobbying with the Governor to get him to veto it. If it does get signed, it’ll be interesting to see if it has the intended effect.
The otherwise sensible people I know who are still on Twitter all say it’s because of a specific interest or group, and the community of people around it who are all on there as well. They all hate what it’s become but put up with it because nobody is sure where else to go.
There’s also a sense of FOMO when it comes to realtime news updates. Until government, news media, and personalities go somewhere and take all their followers with them, it will be hard to break away.
As long as they stay away from public ‘channels.’
There lie dragons.
EFF recommendation on Ad Tracking: https://www.eff.org/deeplinks/2022/05/how-disable-ad-id-tracking-ios-and-android-and-why-you-should-do-it-now
When Sonos first came out, they had this really easy to use, standalone device. It had a track wheel like the old iPods, buttons, and a color display. That made it easy for non-tech people to browse and choose what to play. Then they decided to drop that and go the app route. It’s been downhill ever since.
There are basic rules for coming up with these types of product subscriptions:
Now apply these to seat warmers, suspension adjustments, self-driving, or whatever else shows up in the future. If you don’t hit all three, head back to the drawing board.
P.S.: This isn’t limited to cars. It’s equally true for any hardware product.
I’m really curious about the profile of who is still working there and their reasons for being there. Not speculating. Just the facts.
I just posted a link to a review by someone who has been playing with it for a while and talks about a lot of use-cases: https://lemmy.ml/post/18938549
Ed Zitron’s take: https://www.wheresyoured.at/burst-damage/
This topic came up when self-driving was first coming up. If a car runs over someone, who is to blame?
Most of these would likely be indemnified by all kinds of legal and contractual agreements, but the matter would still stand that someone died.
Just spent a week manually moving everything off Authy. Total pain, but there are lots of better solutions out there now.
I’vd tried multiple times to convert existing code or createnew ones using LLMs. The first attempts are OK, but once you start refining the prompts, they all go off-the-rails.
Most of the time, the generated code uses old or deprecated libraries or APIs. You point that out and they correct it. But a few iterations later, you’re refining something else and the old, deprecated calls come back. Once again, you point it out and it gets corrected.
Forget trying to correct it yourself by hand, because now it’s diverged from the LLM context. And this can happen in multiple places in the code. Rinse. Repeat.
At some point you just give up. Either it’s wrong or it will be wrong in different ways later. You have to read through every line to find strange, divergent errors. Over and over. It gets exhausting.
At the end, it feels like maybe you could have done it faster and more quickly yourself, but the time has already been sunk.
Anything they go after today is 18-24 months out. Chasing after AI would be pretty risky. Desktops and laptops are moving to ARM and RISC-V. Their best bet is to go after whatever enterprise data centers will need a couple of years from now.
If I were laying bets, it would be to go after power and heat efficiency. Like, hard. Take their time out in the wilderness, then come back with chips that save the planet from climate collapse.
Last time, it didn’t go so well for the robot:
https://www.theverge.com/tldr/2017/7/17/15986042/dc-security-robot-k5-falls-into-water