But it sure feels nice to blame your enemies instead, doesn't it? Let's all pat each other on the back that we're the victims, and only if... and leave it at that.
Way to show you really, really don't understand the politics of Latin America and who funds the various interests that run the show.
> Every recruiter has spreadsheets of blacklisted employees
If you're going to allege illegal anti-poaching agreements, you ought to provide evidence of those claims.
> So illegal en CA but legal pretty much everywhere else, once again limiting you if you want to move because COL is too high in California and reducing the pool of real employment alternatives.
Actually, I just checked this and in 2024 the FTC banned non competes nationwide.
> Software jobs but not gaming jobs. California suffers from an artificial shortage of affordable housing due to insane tax laws and building restrictions. There's nothing free market about this.
And? Id software developers are free to work non-gaming software jobs. A big part of the reason why game dev jobs offer less renumeration is because people are passionate about games and are willing to take a pay cut to work in the industry.
If an Id employee is not willing to work non-gaming software development jobs that's a restriction imposed by their own decisions, not by their employers.
People in this thread are comparing Id software developers to slavery. The fact that they'll have to go on COBRA in between jobs doesn't make this comparison to slavery any less absurd.
Yes because companies are famous for being highly law-abiding under every circumstance and every major instance of corporate fraud has been identified and properly punished at a criminal basis.
C'mon man, the US is a country where wage theft is 3 times higher than all other formst of theft combined. Informal blacklists are as simple as keeping a notebook in writing and letting people know through hidden WhatsApp channels.
> Actually, I just checked this and in 2024 the FTC banned non competes nationwide.
The rule is vacated by an injunction.
> And? Id software developers are free to work non-gaming software jobs. A big part of the reason why game dev jobs offer less renumeration is because people are passionate about games and are willing to take a pay cut to work in the industry.
I have no idea why you think that a job being desirable and in high demand means that the people who effectively perform the job are somehow less deserving of workers' rights. The entire point behind having workers' rights is that basic job affordances and rights a non-negotiable because we do not allow certain forms undignified work.
Benefits are part of an employees compensation package. A competing offer could have even better healthcare than Id.
> Industry blacklists to exclude uppity employees and union members.
This is illegal and the last time SV companies were found doing this the government punished them
Is there any evidence that this is happening to Id employees?
> Noncompetes
Illegal in CA where ID is based. NDAs don't prevent you from working at competitors, only from taking confidential info.
> Extremely localized jobs and an ever-shrinking number of larger and larger conglomerates as employers.
Id is located in the Bay Area, probably the place with the greatest concentration of software jobs in the country if not the world.
If a period of unemployment kicks you off an insurance program that's covering life-essential treatment for a loved one, there is no mechanism of "choosing freely" here; ex-employees don't have the option of covering health care themselves and there are no guarantees that the other employer's health care will cover existing treatments even if the coverage is better in theory.
> This is illegal and the last time SV companies were found doing this the government punished them
Every recruiter has spreadsheets of blacklisted employees, one of the reasons why companies frequently outsource staffing to outsides for plausible deniability.
> Illegal in CA where ID is based. NDAs don't prevent you from working at competitors, only from taking confidential info.
So illegal en CA but legal pretty much everywhere else, once again limiting you if you want to move because COL is too high in California and reducing the pool of real employment alternatives.
> Id is located in the Bay Area, probably the place with the greatest concentration of software jobs in the country if not the world.
Software jobs but not gaming jobs. California suffers from an artificial shortage of affordable housing due to insane tax laws and building restrictions. There's nothing free market about this.
Yes, there are scenarios where employees are stripped of agency. E.g a factory owner taking and holding foreign worker's passports. But if you're going to allege that something is preventing these works from accepting competing offers, you have to offer evidence for that claim.
* Employer-bound health insurance in the US
* Industry blacklists to exclude uppity employees and union members
* Noncompetes and NDAs
* Extremely localized jobs and an ever-shrinking number of larger and larger conglomerates as employers
An econ 101 observation: unions contribute to structural unemployment: Keeping wages above market-clearing levels, and by preventing wage adjustment.
Through collective bargaining, unions can negotiate wages that are higher than what the market would naturally set. This can lead to the cost of labor being too high for some employers, resulting in fewer jobs. Similarly, unions can prevent wages from adjusting to market conditions.
So for the common good, individuals may go without a job.
Econ 101 observations are utterly useless without the specific context in which they're made. This is like talking about spherical cows in a vacuum in the context of aerodynamics.
In the specific case of unions, they always forget to mention that a higher proportion of a company's income going to salaries generally means increased consumer spending for workers, which spurs other kinds of industry and services that may mean a net benefit for the global economy.
Of course second and third-order effects are not really talked about in Econ 101.
…
> I vouch for the code that I write or that I delegate to an LLM, and believe it or not it doesn't take a magician to write a k8s spec file…
I have been writing code since 1995.
That has zero relevance to my skill at rolling out deployments in a technology I know nothing about.
One of the two things you’ve said is false:
Either a) you do know what you’re talking about, or b) you are not confident in the results.
It can’t be both.
It sounds to me like you’re subscribed heavily into a hype train; that’s fine, but your position, as described, leaves a lot to desired, if you’re trying to describe some wide trend.
Here my anecdote: major cloudflare outages.
Hard things are hard. AI doesn’t solve that. Scaffolding is easy; ai can solve that.
Scaffolding is a reliable thing to rely on with ai.
Doing it for K8s configuration, if you don’t know k8s is stupid. I know what I’m talking about when I say that. Having it help you if you do know what you’re doing is perfectly legit.
Claiming it did help when claiming you have, and I quote, “zero knowledge” (but you actually do) is hype. Leave it on LinkedIn dude. :(
You've been coding for a lifetime yet you don't seem to get that certainty in software is a spectrum? I have sufficient confidence in the output of LLMs to sign my name under the code it writes when putting up a PR for a specialist to read. That's good enough for 90% of the work that we do day-to-day. You think that's not hype-worthy?
> Doing it for K8s configuration, if you don’t know k8s is stupid. I know what I’m talking about when I say that. Having it help you if you do know what you’re doing is perfectly legit.
"Knowing" k8s is an oxymoron. K8s is a profoundly complicated piece of tech that can don insanely complicated things while also serving as a replacement for docker-compose or basic services that could have been hosted on ECR. The concepts behind basic k8s functionality are not difficult, but I saved myself two weeks of reading how to write helm spec files, a piece of knowledge I have no interest in learning because it doesn't add any appreciable value to the software I produce, and was instead able to focus on getting what I needed out of my cluster automation scripts.
This really isn't that complicated to understand. I don't care for being a k8s expert and I don't care for syntactical minutiae behind it. It isn't hype that I now I only need to understand the essential conceptual basics behind the software to get it working for what I need instead of doing a deep dive like I had to do years ago in when reading similar docs for similar IaC producs to get lesser functionality going.