It's actually a fairly frequent fact of programming language development that type resolution can change across versions. Haskell famously has a ton of extensions that enhance the type system in various, potentially incompatible ways.

In fact the question of whether a code type-checks is itself undecidable.

Curation was implicit when the cost of image creation was high and authors had to consider the photos they were taking beforehand. Now curation comes afterward.

> That the anti-Israelis are going to latch on it as proof that Israel is evil is an unfortunate side effect. There is never a clean war and certainly not the kind of war that has been fought in Gaza.

That and the abundant evidence of genocidal intent in Gaza and the explicit ethnic cleansing of the West Bank with full support of the Israeli society is the reason why it is evil. This incident is one of literal hundreds.

Well yeah. I went to a world-class research university in Latam. The brightest kids were making using of internships to Google, Microsoft and Meta a couple years before graduating and by then they already had a career path laid out for them in the Bay Area.

I'm sure a bunch of companies took advantage of the H1-B program, but without a doubt it took most of the best talent too.

It's bifurcated. Big Tech used it to increase the labor pool local to their existing development centers. The consultancies used it to drive down unit costs.

You work on niches that have very specific requirements that you can only derive from having a good relationship with customers and so you attend to those needs faster than competitors who are out of the loop.

> you attend to those needs faster than competitors

I wonder if this type of hustling can be called moat building?

The question to ask is, better than which human?

The top 25% percentile of coders in my org definitely code better than most agents. The rest? I trust the output of an LLM to be far more consistent when adding/deleting features across service layers than a human that can create accidental typos. Same thing with bog-standard React components or Docker build scripts.

> I've watched teams go from deploying weekly to deploying 5x/day after adopting AI coding tools. Their velocity metrics looked incredible. Their incident rate also tripled. Not because the code was worse per se, but because they were changing more things faster than their observability and testing could keep up with.

But this an improvement! The features/incident rate improves as you have more incidents but fewer in relation to the increased velocity. This may or may not be a valid tradeoff depending on the impact of incidents.

At least in my org we have an understanding that the product side will have to change drastically to accommodate the different rates of code development.

Documentation can be fairly rote, straightforward and can have a uniform style that doesn't benefit from being opinionated.

Power exists whether you like it or not and when power gets away from decisionmaking you just generate a power vacuum.

Power needs to be placed in the hands of better decision-makers. That starts from getting money out of politics.

Paving the way for arbitrary detentions and concentration camps.

These are already arbitrary detentions, well unlawful at least (they're purposeful, just not for legal purposes).

The tens of thousands of detainees aren't being put in hotels... they're going to concentration camps; either in USA where they're forced to work (slavery you might term it, as many (most?) have not broken the law, nor been detained legally); or abroad where the regime's intention appears to be that they die.