shmichael

Stack management: automatically rebasing all dependent PRs on any downstack change. Ability to view & navigate the stack in the reviewer UI. Ability to merge a whole stack with one command.

No one is forced into buying the product, so it feels like an emotional rather than a rational rant from OP.

So you argue we discriminate based on who/what wrote the code, instead of what's in it?

Let's take this to a different domain, self driving cars. Would you equally argue for human driving? I'm pretty sure over time it will become clear to everyone that machines will be able to outperform humans consistently at this task, to the degree that human driving will become illegal. But for now the press likes to focus on any failure of machine driving, taking for granted human drivers are the largest or second largest cause of premature death in many countries.

Coding (in many ways, but not all) is a more open ended and versatile task than driving, so it's natural that current iterations seem untrustworthy, but ignoring the trajectory is erring on conservatism, and doesn't seem to me to be grounded in any sound reasoning.

Imagine military instructors would say that it's important to focus on cavalry and bayonette use just because they can't figure out how to adapt their curriculum to the new reality.

World war I was very much that.

On the other side of every "useless war" is the what if question. Killing Hitler before WWII would have been seen as a cruel interference with German sovereignty.

Anyway it would be wise not to tie social network corporate affairs to the war. The two are not linked in a more significant way than a social network in general being linked to such affairs as a media.

Without the purchase price, it is unclear whether this deserves congratulations or condolences.

Two years in the LLM race will have definitely depleted their seed raise of $4m from 2023, and with no news of additional funds raised it's more than likely this was a fire sale.

It's a lesson as old as history: You either exit a hero, or live long enough to become the villain.

I'm trying to understand, would jj's first class conflicts solve the issue of having "stacks" of PRs that can easily be updated at any point in the stack? This is one of the features most absent from git, but prevalent in Google's tooling as well as Meta's. The only good known solution I know is graphite.dev

Inventing the automobile has clearly made humanity less fit. Should we stop driving?

No. Going back to the stone age is not the solution. For the majority of our day, commuting without a vehicle will be impractical. So will coding without AI, especially as AI improves.

To retain human competency, we will have to find a novel solution. For walking, we created concentrated practice time - gyms/outdoor runs. Some evolution of leetcode, or even an AI guided training, might be the solution for coding skill preservation.