turpentine

I've seen these people rapidly disappear in the last 5 years at a big tech co. Old UNIX heads that had experience back to the 80s being made redundant. Who is replacing them? Mostly offshore 20 something year olds on a fraction of the salary a tenured person had, being told to just follow runbooks, pasting the runbooks into Claude or ChatGPT. These people can't explain anything, didn't really cut their teeth on doing things out of curiosity, and if asked a question, will just be playing copy-paste-back-and-forth with a LLM.

Year of the sel4 desktop, when?

People who know less and have less experience doing things they don't understand are not likely to be associated with quality output.

reddit has been banning reddit accounts of people who use public cloud services as a vpn i.e. while travelling or in cafes, without recourse. Reddit's answer was afaik "don't do that, and create a new account."

I had plenty of backing under the original org to operate that way, but acquisition restructuring often means managers at multiple levels exiting. When I was put on garden leave pending payout, several of my colleagues reached out distressed asking if they should be threatening to quit to force a reversal of the decision, or start looking for other work out of dissatisfaction, and others offered to provide references. I of course thanked them, but said they should look after their own interests as nothing was likely to change.

> From my experience, it's definitely drifted away from a bunch of nerds solving problems to something more towards emotional/personal/politics. I recently saw someone cry when a person very kindly asked them to explain a discrepancy. "Back in my day" people would just state facts, point out flaws, and argue a bit, and have fun doing it, for better or worse.

In the last few years, I ended up at a bigtech co through an acquisition, and had been someone who was a go-between for solving issues across teams by having a good understanding of everyone else's codebases, tests, build processes, deployment, infrastructure etc. This papered over the culture of siloed development, refusals to think beyond single services etc. I would submit tests and patches, along with tickets describing the bug, impact statement, fix, test coverage, risk, and make myself on-call or directly supervise deployment, etc.

Attempting to continue that in an org x25 larger was met with people firing off angry emails to executives saying their authority was being undermined and made to look bad, when long standing issues were made trivial and fixed by "someone they had never met before", and wherever they came from can they please go back to. I have no idea what a lot of these people were spending so long doing, their commit history was often full of changes that would make you go think "???". I guess it's lucrative to run out the clock year after year on a 180k package, attending meetings where you argue that things are difficult and lets meet again in 3 months? After becoming highly visible for bringing things to attention, I was offered a package to leave, I assume so they could go back to a culture of top down authority and silence.

Barrier to entry? It is more or less just arithmetic.

Appeal to hypocrisy is not a valid refutation.

Additionally, I would ask what the economic benefits are.

If they are structured to end up running at a loss and generate almost zero tax revenue (i.e. just payroll tax on a dozen full time staff) on large amounts of revenue, is that good for the people of the city/state/country?

Studying and patching binaries has always been done. This is not new.

afaik up to 2020, IE and ActiveX was required for online banking. Past that I heard you had to install a local webserver that the browser could communicate with. I'm not sure if any security issues are mandated by law, but it does sound like a minefield.

You've erased your own voice and evidence of thinking and writing.

Syntax is listed right there in the GP comment. They've given plenty of rope to hang themselves by.

Someone who says that programming is not about working at the level of about data structures and algorithms without LLMs raises red flags.