You forgot profit.

Well if we're looking at tech to put AI data centres in space, space based power won't be far behind .

An possible avenue of terrestrial nuclear power obsolescence maybe that we're going to need as much nuclear power as we can get in space where we really can't do solar because it's so far away. That is a consideration within the service lifetime of any type of reactor you'd build today along with the possibility it may kill the very community it employs.

It maybe that the two combined create options that no one really saw coming.

Maybe we can think of another way to piss off Israel that doesn't involve crazy human rights abusing Iran having nukes. Maybe something to do with Bacon or working on a Saturday.

Is that you?

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

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

Democracy is for retards.

Government did this. All of this. Government regulated so much that only a rare few can afford to compete.

This is late stage statism. Retard voters are to blame.

Like you.

I am not 100% sure. IIRC (from reading it somewhere) I think it makes it worse because the fire spreads and acts like a liquid.

Californian's are only at the beginning of their experience with eucalyptus trees, which are native to Australia. You're quite right, it's possible to build bushfire ( I think the US calls them wildfires) resistant homes. In Australia there are specific assessment and building requirements for a home likely to be affected by fire called BAL and I think you also have to get a planning permit

I had the experience of my neighborhood having a bushfire go through it. I realized how few people know just how terrifying the situation is when they asked "can't you just put it out with a garden hose?".
Not quite, the flames were 4-6 stories high, when it hit my neighborhood 18 houses burned down in about as many minutes. Generally a bush fire will have embers fly a few kilometres ahead of it, which is where you can try to stop it. The really bad ones create their own weather which looks like a firestorm and the worst ones creates a fire tornado, which is basically a small tornado throwing the stuff burning in it around.

This fire was stopped from getting my house by an empty block of land and a chopper hitting it with 10 tons of water. High BAL houses survived next to houses that were burning and have things like sprinkler systems on the roof that extinguish embers. However even if your house doesn't burn, the heat melts curtains to the glass, paint peels off interior walls.

You have no idea it's coming sometimes, we got about 5 minutes notice to evacuate, people literally escaped their homes with what they were wearing. I prepare my house for bushfires by cutting back the garden and we have go bags with clothes and important documents. I still have more to do though.

Fortunately there wasn't a loss of human life, lots of people pets panicked, ran before their owners could grab them and died - few people saw that coming. My poor neighbor, came home from breakfast with his wife to see his house on fire, they lost everything. My neighborhood is a ghost town now, people I've know for a long time just gone and it's a special kind of fucked to watch their houses being taken away in a skip bin.

If this thing helps even a little, I'd use it.

Using it to fight fires in space might become a good application of this. I remember experimenting with 100 watts of 100Hz at about meter made it difficult to breath, however that was easy to hear.

I get sick after 10 minutes last time I tried it (a few years ago). It's not anywhere near solved. Of course I have no desire to try the new versions, because even if it was solved it doesn't actually make anything useful better.

I can tell you a definite NO on that one because of recent work with the Betty Boop licensor, they very focused on protecting their brand.

Just as Open Source should be so that it continues to attract developers. Seeing stories like this validate the strictness in GPL3. The constant efforts to subvert the GPL really shows contempt for the developers and contributors.