Oh, but these are *preventative* wars. He gets a peace prize for every country he invades!

Venezuela was using fentanyl as a WMD. Iran was about to nuke us. Cuba might attack us with drones if someone provides them. Greenland might start a snowball fight, and make us look bad if we lose.

Presumably we've got all our best people on this, since they're obviously not on the UFO videos.

One of the "unidentifiable" objects in an earlier release (last year, I think) was obviously as hell two birds flying low over the ground.

I don't have a conspiracy theory to explain it, but this is all utter bullshit.

Linux?

Scalping isn't, and shouldn't be, illegal. You own the ticket, you should be able to do what you want with it, including reselling it.

And no, getting rid of scalpers wouldn't make ticket prices higher. Scalpers exist because the concert ticket prices are lower than what the market will actually bear. If a theater full of people are willing to pay 1K for a concert and they sell the ticket for 500, a scalper can make a profit via arbitrage. The only actual way to get rid of scalpers is to raise the prices to the sky (like 2-5x current prices) and slowly bring down prices over time until they're all sold. But my guess is you probably wouldn't like that any better, as the end price would likely be higher than the current scalpers price.

At least it's not more Star Wars slop.

Only if you say it's OK elsewhere.

To train an LLM during flight.

Since when did product longevity matter?

Since when did employees matter?

I'm amused at how petty that billionaire's make-money-fa$t schemes are. Selling steaks? Tennis shoes? Bibles?

What other billionaire does this to get richer?

Ah, binary.

No, it's more about how teams work. Teams have a scope. They don't typically go beyond that scope. So if my team owns the Foo and Bar modules, I work on those. But if there's little important work on Foo and Bar, but a lot of important work to be done on Baz, it's generally organizationally difficult for us to work on Baz. Typically we need to be lent out by our manager and seconded to the other team. Which can be a lot of red tape and politics.

Now if you're imagining some alternate world where programmers an be moved at will- then we're already one big team instead of multiple small teams.

And no, a smaller team doesn't win every time. If it did, then then smallest team possible is teams of 1 and we'd all do that. There are sweet spots, which depend on the organization, the work to be done, and the importance of that work. For some that's bigger, for some smaller. I've definitely worked on teams that were both too small for the work, and that were too big.

They can, under some circumstances. If the scope of what they work on is too small to fill the team's feature set. Or if the work they would be doing is significantly less important than other work to be done, having them in one large team makes it easier to move to more important work and can get critical features built faster. In that case it may not be overall more work done, but it may move the important stuff quicker. If larger teams weren't useful on some level, we wouldn't have teams at all- we'd all be individuals.

They're one of the 4 biggest stock brokers in the US. If you aren't trolling, you're showing yourself to be really ignorant.

In the end- good engineers with sufficient experience and support will get stuff working with any methodology. Bad ones or ones insufficiently supported will fail with any methodology.

There are some things that agile works well for, but it's really limited to domains where you can quickly build something tangible for feedback and you have stakeholders willing and able to give frequent feedback. UIs are a good example. It's a horrible fit for anything that requires actual research, or that can't be shown to low technical knowledge customers frequently (in other words anything that actually needs weeks or months of backend work, algorithm writing, or infrastructure to be written).