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.

Even worse, it installs a special Excel that you can only access through Solitaire, but which still takes up all of the space of normal Excel.

I use Firefox with UBO and occasionally youtube gets mad for a day or two, then it works again. Yes, I've run updates manually.

I still recommend it as long as it works, though.

Sadly I can't recommend Firefox for mobile any more. It crashes on me every day, sometimes multiple times, when using javascript-heavy sites.

You were so close. It's obvious you post as a coward because you're stupid.

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).

The problem with that is the skills needed to manage and the skills needed to do real work (let's take programming as an example) are pretty distinct. Someone can have both, but they tend to have one or the other. Forcing those without the skills to do the practical work into doing it doesn't actually help the team, it just slows everyone down. And if they get on the critical path of any project you can be royally fucked.

There are a couple of ways to solve this problem:

1)Larger team sizes. This can work if the team owns enough to keep everyone busy, but it can lead to effectively being independent subteams calling themselves one team while being inconvenienced by each other.

2)Each manager managing multiple independent teams. This can work if it doesn't overload the manager. The biggest problem is when the manager decides one team is more important and doesn't support the other(s) enough. This works better the closer the teams are, as it requires the manager to know fewer sets of collaborators and politics

Oh look it got mad I insulted its sock puppet

It is when they get it, but I'm not sure you understand the purpose of an archive

It would be useful if they were required to make any training data they didn't pay for publicly accessible...

But they aren't

Don't worry, I have no illusions about reaching him. This ain't my first rodeo where he's the bullshit

Except you can't trust that Google's browser isn't snitching anyway, so no, it's really just a way for Google to keep you using their service without having to process your tokens

It's the techbros who don't understand it, obviously. You agreed to install one thing, they took it as permission to install another thing. Conversely, they also offer to support you, then they release the same product under another name and tell you to go fuck yourself. That shit is fucked both coming and going and you're here to defend it.

"that military is stopping a nuclear armed terrorist state from setting the worlds trade rules."

No, it isn't. America has been setting those rules for decades, and if you don't like it, we will invade you. We are the only nation to ever nuke anyone. We are the terrorists.