Earlier quoted context omitted.
Yeah "work from home" largely means "work from more affordable real estate". Very very few people do I know who work from home do it for digital nomad type reasons. Everyone else is due to not being able to afford anything near the office.
Each and every parent of 4+ whom I worked with lived in the middle of nowhere and would only emerge from the deep woods for an occasional workshop a few times a year. It's a lifestyle impossible if one has to show up an hour's drive away, every weekday.
What if remote working, not AI, is to blame for weak junior hiring?
311–320 of 394 posts
Re: What if remote working, not AI, is to blame for weak junior hiring?
#312Earlier quoted context omitted.
Ever heard of social engineering? Also, models nowadays are way sharper than they were even a year ago. They’re not going to make stupid mistakes like that unless you basically ask them to. GPT-5.x for example would bend over backwards to avoid even reading your passwords into context.
> Ever heard of social engineering? Oh wait, I thought these things were super smart. I didn't expect "social engineering" to work on them. > models nowadays are way sharper than they were even a year ago. You are missing the point. If the thing can solve complex math problems and at the same time be so dumb as to fall for "social engineering", then that means that it is not "smartness" or "reasoning" that is helping…
I'm not just trying to be snarky, but I have no idea how to read this without taking the implication that humans are advanced, yet dumb, search algorithms.
Re: What if remote working, not AI, is to blame for weak junior hiring?
#313Earlier quoted context omitted.
ZIRP alone isn’t even the full financial story - there was a time bomb tax change from a 2017 bill that impacted R&D (most software work) and that took effect in 2023. But it’s fairly visible that big companies (eg Meta) that are spending a lot on AI are actually changing spending on headcount and hiring to maintain margins. It’s not the efficiency of the workers, it’s the maintenance of margins with big new spending…
The layoffs are happening all over, not just in USA. Atlassian has cut jobs. Spotify. Wisetech. Xero. It's happening all over. This is not a USA tax policy problem.
Re: What if remote working, not AI, is to blame for weak junior hiring?
#314Earlier quoted context omitted.
ZIRP alone isn’t even the full financial story - there was a time bomb tax change from a 2017 bill that impacted R&D (most software work) and that took effect in 2023. But it’s fairly visible that big companies (eg Meta) that are spending a lot on AI are actually changing spending on headcount and hiring to maintain margins. It’s not the efficiency of the workers, it’s the maintenance of margins with big new spending…
The layoffs are happening all over, not just in USA. Atlassian has cut jobs. Spotify. Wisetech. Xero. It's happening all over. This is not a USA tax policy problem.
Re: What if remote working, not AI, is to blame for weak junior hiring?
#315AI is not responsible for anything at the moment, except making existing senior developers reasonably more efficient for sleeve of tasks, but not the tasks that take the most time. Saying "we don't need as many staff because AI" is an oft-repeated trope because it sounds like a reasonable excuse to fire people. It's nearly impossible to back up the claim with any measurable method, and investors will look aside on th…
The narrative "we don't need as many staff because of AI" is a labor disciplining device whether or not it is true. Remaining engineers, loaded up with more projects under the threat of layoffs and with no outside opportunities, work nights and weekends to get them done. Then it is literally true that we accomplished more with less. And in a sense it is even "because of AI." But not in the way that you're supposed to…
Re: What if remote working, not AI, is to blame for weak junior hiring?
#316AI is not responsible for anything at the moment, except making existing senior developers reasonably more efficient for sleeve of tasks, but not the tasks that take the most time. Saying "we don't need as many staff because AI" is an oft-repeated trope because it sounds like a reasonable excuse to fire people. It's nearly impossible to back up the claim with any measurable method, and investors will look aside on th…
Apparently there has been some AI-caused firing on companies that spent so much on AI that needed to fire people to make their short-term numbers not break. From the way people are talking, Facebook seems to be in that category. There is probably some AI-caused firing coming soon on companies that vibe-coded so much that people abandon their products. I expect Microsoft start is on Github. I have been repeating for m…
The observation that AI layoffs would be self-fulfilling prophecy is one I haven't heard before but I'm inclined to agree with it.
Re: What if remote working, not AI, is to blame for weak junior hiring?
#317Earlier quoted context omitted.
Fully agree. I'm all for remote work. However, in my first 2 years of programming, being able to go the the office, put my laptop and notebook down next to a senior dev, point and say, "Help me," was so valuable.
Part of being in the office is that you pick up on what's going on around you. Coworkers might discuss some issue and you might decide to listen in, and so on. That's the bit I really notice I am missing out on when I work at home.
It was a bit of drama and the person ended up leaving because they wanted others to adapt to them. I think they ended up in a remote-only company in the end. Very talented developer.
Similarly, being available to stakeholders and colleagues from other teams come to me at any time and get a quick answer was something that ended up being amazing for my career, got me a few lifelong friends and even a cat.
Re: What if remote working, not AI, is to blame for weak junior hiring?
#318Earlier quoted context omitted.
> Ever heard of social engineering? Oh wait, I thought these things were super smart. I didn't expect "social engineering" to work on them. > models nowadays are way sharper than they were even a year ago. You are missing the point. If the thing can solve complex math problems and at the same time be so dumb as to fall for "social engineering", then that means that it is not "smartness" or "reasoning" that is helping…
> If the thing can solve complex math problems and at the same time be so dumb as to fall for "social engineering", then that means that it is not "smartness" or "reasoning" that is helping it to solve those problems. Just some form of advanced, but yet dumb, search algorithm. I'm not just trying to be snarky, but I have no idea how to read this without taking the implication that humans are advanced, yet dumb, searc…
An LLM will happily say X and behaves in contradiction to X. Because it does not reason. Its behavior is not derived from things that it claim (or appears) to know.
Re: What if remote working, not AI, is to blame for weak junior hiring?
#319Earlier quoted context omitted.
> Ever heard of social engineering? Oh wait, I thought these things were super smart. I didn't expect "social engineering" to work on them. > models nowadays are way sharper than they were even a year ago. You are missing the point. If the thing can solve complex math problems and at the same time be so dumb as to fall for "social engineering", then that means that it is not "smartness" or "reasoning" that is helping…
By "heard of social engineering?" I meant that humans are vulnerable to malicious input too. Prompt injection is basically a simplified form of social engineering for language models. It looks different because models operate over much smaller and more explicit contexts than humans do and are explicitly trained to follow instructions, but the general idea is similar: malicious input tries to manipulate how the system…
No they are not. Social engineering won't work on a human security expert who knows and understands the implications of the information they are giving away. Your analogy is pointless.