Agile tries to solve this differently.

First and foremost, it puts you into tight-knit communication with your team and the customers, so just ask if anyone remembers why it is like that.

If no one does, then Agile enables to basically fuck around and find out.

Which is to say, change it to how you think it’s supposed to be and see if anything breaks / anyone complains. If that happens, Agile allows you to react quickly, i.e. to change it back and quickly release a fixed version.

But yeah, as the others said, if your team feels like documents work better for them, then do Agile and documents. That’s why retrospectives are an integral part of Agile, because it’s not a perfect plan how to work together. You’ll know best what works in your context.

What is this article talking about? That’s a UX change. It has nothing to do with privacy or Mozilla’s commitment to privacy.

Quantum computers won’t displace traditional computers. There’s certain niche use-cases for which quantum computers can become wildly faster in the future. But for most calculations we do today, they’re just unreliable. So, they’ll mostly coexist.

I imagine, you guys might be measuring with two different scales. Early Windows versions were fine, but even back then, a switch to Linux would give you so much more customizability to actually make it yours.

This is a dumb anecdote, but I switched to Linux from Windows 8, and pretty much the first thing I did, was to figure out how to hide the window titlebars. Mostly because I realized, I could, but they also just took screen space away on my laptop.

Yeah, that was basically my reaction, too. There was also some news that the CEO would now be taking responsibility for security, which had me similarly questioning what the hell they were doing so far.
Surely, the CEO is responsible for everything. So, did they just completely forget that security is also part of that?

They did tell their employees to prioritize security above all else, right before not doing that.

You mean like how they told their employees to prioritize security above all else and then had effectively none in Recall?

Man, I always thought the bigger SUVs looked like those oversized clown shoes, but the size comparison picture does drive home just how much dead air is in them.

iAI

(…will always love you 🎵)

Nah, I’m not ignorant, just cynical.

I make digital music myself. I’ve had that moment myself, where for a quick moment I thought, surely there could be some ‘proper’ way of rotating an audio source around your head.
And well, there is not, it is always just an effect thing.

As in, even in reality, our hearing is literally stereo, because we’ve got precisely two eardrums, two membranes that do the detection. Yes, the ear flaps shape the sound, but you can do the same shaping with just effects. Make it a bit more muffled when it comes from behind, for example, and hope you don’t need to also portray that something muffled comes from the front. And of course, always slap a heavy virtualizer effect on there.

In the end, it’s smokes and mirrors that our brain then interprets as something spatial. I don’t have a problem with smokes and mirrors. I do still find it humorous, though.

I enjoy how “spatial audio” makes it sound all fancy, even though it’s just stupid stereo.

They had written that you could fit the entire world’s waste on a football field. I had not interpreted that as specifically referring to high level nuclear waste.

It’s not toxic, nor is it in their backyard.

It is toxic and they wrote “NIMBY”, which means “not in my backyard”, which is what I used figuratively here.

What issues?

Depends on the location. In Asse, there is water entering into the caverns, for example.

Good thing we don’t need to.

You should inform the BGE about it. They’ll be glad to hear all their challenges are solved.

That shit still needs to be stored. I do not know, why you’re berating me about it.

I mean, can you blame them? Why would anyone want toxic waste in their backyard? Not to mention that the search is mainly conducted by companies, which have a vested interest in not making all the issues transparent.

Having said that, I am not aware of the ‘scientists’ coming up with good suggestions either. Gorleben got hemmed and hawed around for the longest time, but its selection process was non-scientific from the start.

It’s genuinely not easy to find a location where anyone would be willing to claim that it will remain unaffected by geodynamic processes for millions of years. And we don’t have a big desert or some other unpopulated area where you could chuck it without political opposition, when it’s not 110% safe to do so.

Unfortunately, there’s not much structure to these, no. It’s nuclear waste from the 60s and early 70s, when there were practically no safety laws in place yet. They just got dumped down there in steel barrels. In a salt mine, which now has water entering it. I’m hoping, the barrels got at least filled up with concrete, but I have no idea.

In Germany, we’ve got a location with 47,000 cubic meters: https://www.bge.de/en/asse/
That requires some pretty tall stacking on that football field. Or I guess, you’re saying if you’d unpack it all and compress it?

Also, we really should be getting the nuclear waste out of said location, since there’s a known risk of contamination. But even that challenge is too great for us, apparently.
Mainly, because we don’t have any locations that are considered safe for permanent storage. It’s cool that Switzerland has figured it out. And that some hypothetical football field exists. But it doesn’t exist in Germany, and I’m pretty sure, Switzerland doesn’t want our nuclear waste either.

Traditionally (as in 20+ years ago), software got developed according to the Waterfall model or V-model or similar. This required a documentation of all the requirements before a project could be started. (Certain software development fields do still work that way due to legal requirements.)

This was often a failure, because the requirements did not actually match what was needed, not to mention that the real requirements often shifted throughout development.

Agile, on the other hand, starts out development and figuring out the requirements pretty much in parallel. The customers get a more tangible picture of what the software actually looks like. The software developers also take over the role of requirements engineers, of domain experts, which helps them make more fitting software architecture decisions. And you can more easily cancel a project, if it turns out to not be needed anymore or whatever (which is also why a cancellation percentage is misleading).

The trouble with Agile, on the other hand, is that projects can get started with really no idea what the goal even is, and often with not enough budget reserved to actually get them completed (obviously, that may also be a failure state; if the project is promising enough, customers will find the money for it somewhere).
Also, you do spend a lot of time as a software dev in working out those requirements.

But yeah, basically pick your poison, and even if people like to complain about Agile methology, it’s what most of the software development world considers more successful.

I feel like that’s the same underlying issue: The requirements are not understood upfront.

If a customer cannot give you any specific information, you cannot cut any corners. You’re pretty much forced to build a general framework, so that as the requirements become clearer, you’re still equipped to handle them.

I guess, the alternative is building a prototype, which you’re allowed to throw away afterwards. I’ve never been able to do that, because our management does not understand that concept.

I’m not here to argue that Linux is flawless if you just do this one obvious trick, but rather to say, for you in particular, with the issues you described: You might enjoy openSUSE more.

It comes with filesystem snapshots out-of-the-box. As in zero setup. And you can rollback to a previous snapshot from the bootloader, even if your system does not boot anymore.
So, assuming neither your filesystem nor hardware broke (and you noticed the breakage right away), it takes 5 minutes to get back to a working state.

It also comes with an extensive system settings GUI, called “YaST”. It certainly does not completely absolve you from touching config files. It also will not make you weap from how intuitive of a GUI it is. But it is a GUI and it covers lots of the common stuff that one might tweak on a computer.

I do also find openSUSE to be less error-prone than Ubuntu in general (my workplace makes me use the latter).

Main downside of openSUSE: It is more niche. The community is smaller. When you do run into an error, there’s fewer articles out there to help you. In particular, setting up specialty software like DAWs, VSTs etc., you may find less help for.

But the small community is more tight-knit and consists of lots of folks with higher expertise, so if you ask in the forum or some other place where the community hangs out, you will usually still get rather excellent help (and perhaps better help than what search engines unearth these days).