I feel like this one is going to fly over a lot of heads. Bravo.

I mean, Agile doesn’t really demand that you do or don’t use tickets. You can definitely use tickets without scrum.

Just a SWE baffled by people who have no idea what they’re talking about farming upvotes by demonstrating “The Internet is a series of tubes” levels of cluelessness.

Yes, I’m sure the phds and senior SWEs/computer scientists working on LLMs never considered the possibility that arbitrary code execution could be a security risk. It wasn’t the very first fucking thing that anybody involved thought about, because everybody else but you is stupid. 😑

One of the biggest areas of ongoing research is about incorporating data from outside systems, like databases, specialized models, and, other specialized tools (which are not AI based themselves). And, yes, modern models can do this to various extents already. What the fuck are you even talking about.

Eh, not really then. If you have some behavior in those 50 copy/pastes that needs to be deleted, you’ve got to delete it 50 times. That’s not easier at all.

Customers tend to view quality more holistically than that, though. Not a lot of people are going to flip their conception of product quality on a single change, but will after a long series of changes. Once a company gets that reputation for poor quality, it’s not as simple as reversing the last corner they cut. It’s a hole that takes a lot of changes to dig out of. More than most companies are willing to reverse.

It does and they’re kinda weird (if you’re used to more like Java-style interfaces). It flips the dependency between the interface and implementor on its head. Worth looking it up, it’s interesting.

Which one is important is going to depend on the context for sure.

If it’s an open source library, they probably won’t care about 1.

If you’re working on internal software used by other developers within the company, management probably really does care about 1 because it’s going to impact their timelines.

If you’re working on a proprietary user-facing API, then even if it doesn’t cost your company anything management might still care because it could piss off valuable customers.

I think that, for what ever decision OP is trying to make, looking at that context is more important than quibbling over what exactly constitutes a “breaking change.”