512 karma · joined June 20, 2024
> like many of these recent layoffs, this is essentially reversing 2020-2022 net headcount growth.
which I took as "this is just reversing Covid overhiring". Which I'm tired of hearing. MSFT might have grown faster in 2021/22, but have stopped hiring for pretty much 4 consecutive years since.
There is a big HOWEVER. At least 2 in fact.
1. The company had been growing in the previous years, 2019, 2018, 2017 (they shrank somewhat in 2015 or 2016). In 2014 they had 29% workforce increase. So the significant growth in 2021/22 is not an aberration but rather continuation of the growth in previous years.
2. What IS an aberration is the workforce count after 2022. No growth in 2023 or 2025 (as in ZERO YoY change), and measly +7,000/3% growth in 2024. And some YoY loss in 2026 (-5,000, or 2.2%). With 2027 YoY likely showing at least some (and possibly a lot) of these 60,000.
So no, "it's just overhiring due to pandemic" was supposed to die years ago.
And the internal memo currently circulating actually does not mention that number so I'd be curious where it came from.
Given all insane bets made by previously (somewhat) reasonable and successful business owners, I wonder how much of a joke it really is...
There was far more serious incident very recently where hackers gained control or attempted to gain control of a propulsion system of an oil tanker. Resulting in a military operation to take it back. People need to start treating these risks more seriously.
Edit: Here's the link to the article:
I'm just saying it wasn't a high value target like a bank. Which is what they counted on.
Unless of course they turn it off without telling the businesses so the products go bad because nobody's watching over the weekend or smth. But then again, why would someone want to do that. I wonder.
Edit: Yes i know the commercial fridges do not have "dials" and it's more involved. Still, if you have physical access to the thing, there's nothing that can be done from the outside that you can't revert.
If I remember correctly OpenAI suspended the testing/training in September after discovering the incidents, so they might be in the clear for now.
So the operators did not have intent to steal the cryptocurrency.
Not that different from me requesting bank transfer through online interface and the software sending my funds to a random person somewhere. As long as the funds are refunded, everything's fine.
Now, if bank IT knew that their software kept making all kinds of bizarre mistakes and instead of fixing it continued to operate it - that would be a different story, and negligence might be at play.
A valid question which has yet to be answered (at least not publicly).
Although at some point it will start bordering on negligence, running software known to do all kind of weird and unexpected things. With each disclosure they're getting closer and closer to that point...
I know we love inventing new words but "stealing" is much more descriptive
>...It [the model] then reasoned with itself that since it found the information publicly, it could use it... it figured that since the wallet it found was public, that "funds could be stolen anytime".
Can someone maybe provide more details as to what actually happened? "the wallet was public"?..
Update: from OpenAI's own report it seems the models found exposed private keys of some Eth developers along with recovery passphrases and thus were able to get access to wallets. Does it qualify as "public wallet"?..
Temperature sensor is a sensor. Refrigeration compressor motor is an actuator.
GPS positioning of a car is a sensor. Motor to turn the wheel is an actuator.
Aircraft altimeter is a sensor. Motors to control control surfaces are actuators.
And so on.
Some devices are sensors, like temperature sensors. It's not that they're "read only", it's that... You can't override temperature. For that, you need other devices. Like a switch to a motor that operates refrigeration compressor. That would be an actuator. If you put the data from the sensor online, the worst case scenario is someone unauthorized gets your data. If you build interface to control an actuator online... You can read the article up top.
The problem is that all major cloud providers (AWS and Azure for sure, and I'm sure Google as well) have a large number of services targeting IoT devices, both to read and control. So default architectural decision is "We'll just plug these into AWS IoT, it's secure, reliable, highly available, and has all the features we need, all we have to do is to configure what we want and we're all set". Which in reality is not that secure just because of how IoT is designed. But AWS/Azure obviously push for these solutions because it gives them more revenue.
That actually made me LOL
And when this results in actuators executing some bad actions they scream in horror "AI went rogue! It escaped the containment!!! It's going to kill us all!!!"
Go fix your software before you let it do stuff online or IRL. It's not "Terminator", it's just bad QC.
Go to the most popular LLM (ie Claude). Give it the job description. Give it your resume. Ask it for percentage match, it will give you a number. Then ask for advice on improving your resume, you can either ask to rework the resume by itself (if you're in a hurry) or you can work with the thing to modify the sections/entries yourself, one by one, if you have time. With each modification you will get better and better percentage match. Ideally you need to get to high 80% or maybe even 90%.
The idea is that automated ranking tools used by recruiters/HR are ultimately use the very same LLM, so you are improving your ranking assigned to your resume by those ranking systems.
I have to add that now this advice is mostly useless as everybody's using the same technique so you won't be standing up against others but merely be on the same level.
Add to it the fact that many job descriptions are inaccurate and sometimes downright misleading, and hiring managers use their own criteria, and you will understand why connections/referrals is probably the only way to get hired now.