This does tally up with what I've been hearing. Where I'm at there's been a few hires straight into senior. I've not heard of an official junior freeze. At the same time it's been a long time since I've seen a new one.
The problem, as I commented prior, is that if we no longer bring in junior devs to gain this kind of experience, we lose the flow of junior -> senior. But in most places, the people making the decisions won't consider anything beyond the end of the current fin year.
I don't think developers are doing it. It's managers making this kind of decision I'd say.
I've been told about companies in the same field as mine with a hiring freeze on juniors. So it's kinda second hand.
I think it goes further than that. There's two things happening with regard to AI and software development.
1: Stack overflow has become less common as a resource to solve problems. This, as you say has a problem of input into LLMs for future problems to solve.
2: Junior developers are being hired less because of AI. I assume the idea is that seniors will use AI in the same way they would usually use juniors. Except, they've done what business always does. Not think one bit about the future. Today's senior developers are yesterdays junior developers.
The combination of AI performance drop due to point 1, and the lack of new developers because of point 2 makes for potentially, a bad future for the profession.
We used to have it terrible in the UK in the 90s and 2000s. Basic ADSL was trialled in 1999 and available in maybe late 2000 I think. But it stagnated for a while.
When it came to fibre, interesting things are happening. As well as the "national" (although privatised) telco installing it, there are many independent companies fitting it. Where I live I have the option of the official telco (1000/110) and a private company (1000/1000). Of course I chose the latter :P
Some people have 3 or more options.
Yeah in the future there might well be a handful of overall winners that vacuum up the losers and carve up the territory. But right now, it's a good time for the normal people... At least for internet.
EDIT: Just to add, some are ISPs and will only sell their own product. Some are wholesale, so even if they're the only company in your area, you can often buy from multiple ISPs through them.
This one threw me off. I'd muted discord by mistake. Weirdly voice still works. I spent ages checking and double checking settings to see why I wasn't getting notification sounds and the ptt sound. Dismissing any mute possibility because voice was working.
When I found it was this....
I'm on a pretty old version of mbin (I have some modifications I made for federation issues back when it was kbin). I need to spend a weekend to pilot an upgrade and make sure I can run it safely live.
But even then it's better in some ways already and I never feel like I'm missing something from lemmy. But I think just calling the whole thing lemmy puts off people that are seeing things through a political lens.
Pretty sure that's only true about Lemmy. There are other threadiverse apps. The mistake is people calling the threadiverse lemmy.
These days with UEFI it's much less likely to break things. Worse case though you just boot from a LIVE USB boot, chroot in and rerun grub/your bootloader installer. Often even if windows puts its own bootloader first, you can choose your bootloader from the bios boot menu and just rerun the bootloader installer.
It used to be a lot worse.
I said elsewhere, I hope this is just some way to track changes over time per user.
But they need to take an anonymous hash of some non changing data or create an install id that is used for this and nothing else (e.g it identifies a unique user but not the person or hardware behind the user).
Too much identifying info is just pushed around like we shouldn't care, it's become a real problem.
The way I read it, the developer wanted opt-out but it's likely it will be opt-in. I'm find with opt-in and vehemently against opt-out for telemetry.
I would prefer the information was statistical only. Rather than hostname (making the assumption they only want hostname to be able to somehow separate the data to follow changes over time), a much better idea would be some kind of hash based on information unlikely to change, but enough information that it would be unlikely possible to brute-force the original data out of the hash. So all they know is, this data came from the same machine, but cannot ID the machine. Maybe some kind of unique but otherwise untrackable unique ID is created at install time and ONLY used for this purpose and no other.
I don't know if they have much of a case to sue you, if you fall through the cracks on their own negligence. Fire you, yes. Sue, I am doubtful most larger businesses would even try. They'd rather solve the problem and sweep it under the carpet in my experience. Not USA experience of course, but still the attitude would be similar I expect.
I would worry a bit about whether they're allowed to give negative references though. Because if so, it might not be so easy to get another job after.
Best move would be to line up another job to start like a month before the review, and never reach the review stage. Even if discovered, most people that would "know" wouldn't really be driven to report anything if they're leaving anyway. The "not my problem, and this will make it my problem" attitude in big companies is real.