I am also @[email protected]
I could have said it better.
I mean compressor as half of a compression/decompression algorithm. The better way I should have worded it is: when you apply machine learning to a compression problem, you can do it lossless…your uncompressed output will be identical to the input, every time.
“NNCP” is a good search term to learn more, specifically about how this works.
This is not new knowledge and predates the current LLM fad.
See the Hutter prize which has had “machine learning” based compressors leading the ranking for some time: http://prize.hutter1.net/
It’s important to note when applied to compressors, the model does produce a code (aka encoding) that exactly reproduces the input. But on a different input the same model is unlikely to produce an impressive compression.
Just switch to the F-Droid version.
Better: make sure all the apps you use come from F-Droid
They do this to juice the gross margin number and make the auto business appear more profitable.
Everything’s computer
I bet the people you work with are very happy to have you as a lead.
I’ve been in this scenario and I didn’t wait for layoffs. I left and applied my skills where shit code is not tolerated, and quality is rewarded.
But in this hypothetical, we got this shit code not by management encouraging the right behavior, and giving time to make it right. They’re going to keep the yes men and fire the “unproductive” ones (and I know fully, adding to the pile is not, in the long run, productive, but what does the management overseeing this mess think?)
To be fair, if you give me a shit code base and expect me to add features with no time to fix the existing ones, I will also just add more shit on the pile. Because obviously that’s how you want your codebase to look.
In my current role, I mostly hire “senior” roles. So the applicants (which are pre screened before I see them) typically have 5+ years experience. I ask about the code they’ve written, and then I ask some questions about how they would extend the code (to meet some new requirements). What I’m looking for is not so much a specific answer, but more so “can we think through this problem together.”
That said, I’ve been the interviewer for “junior” roles…and there isn’t as much correlation between ability and experience as you might think. So no reason to feel imposter syndrome. I’ve worked with extremely smart/talented developers without any formal training.
I think all the stuff you’re doing sets a really good foundation for a career in software, if that’s where you want to go. One thing I might suggest is making a few contributions to open source or team projects. It can be useful to learn about how to read code, and present code to others (or to fit your idea into an existing code base).
I have to do many interviews.
I don’t care if the applicant uses AI, or any other tool available to them. I just care about whether they can explain, debug, and modify/extend code (which they wrote, or at least composed somehow and are presenting as their work).
I’ve definitely been suspicious of AI use, and also had some applicants admit to it. And I don’t count that against them any more than using a web resource.
But, there is a very high correlation between using AI and failing at the explain/debug/modify part.
I feel like this could be a Columbo episode
True, but they were still resource constrained, which might be why they ended up with a model with lower resource requirements.
The scary part to me (noted in the article as well) is less the technical hack but more so the amount of data they are collecting.
Subaru had/has an ongoing issue where the telematics drains the battery while the car is parked, especially if it’s parked out of reach of cell towers. With the amount of data they are sending, it’s not surprising.
There is no need for the car to report its position whatsoever unless I request assistance.
Smiling on the outside…
Should be a nice salary boost for developers in a year or two when all these companies desperately need to rehire to fix whatever AI slop mess they have created.
And I hope every developer demands 2x their current salary if they are tasked with re-engineering that crap.
Yup. If source is not available I’m not using it if I have any choice in the matter. Binary distribution is nice, but I’d rather have source.
Plus I’m sure some kind soul has created a build pipeline that autogenerates binaries from the source. I can always either use that or clone and customize it. It’s a natural separation—as a dev I’d like my responsibility to end at “I merged working code to trunk”.
+1 for feeder
My point was not that X would be able to do something about this, but that it is not a source of breaking news, and fundamentally not a replacement for journalism…and should not be used as such.
The original post has 58k views, the correct information has 2k. That is the level of efficiency that site has in disseminating correct information.
Visual Studio has these issues daily.
Ten years ago VS was awesome. In the last 2 years, all they added is AI crap and every other feature got more buggy.