A metadadjoke!!!

Wow. SNOBOL was one of the coolest, Stange languages.

In that a Gollum caganer?

The question implies that the OP wants to create one giant filesystem with all of their data on it. This has its own issues, especially if it is in /home. For one, as someone else pointed out, it’s fairly difficult to run your system without /home mounted, and that makes it difficult to resize. Sure, you can set up an admin account with it’s home in the /root filesystem and then log into that - but that seems to be a lot of work in itself.

If it was me, I’d set up mount points for file systems that make sense. Maybe /data/Photos, or /data/Music, or data/AppData, or whatever. As much as possible, I’d just point whatever software I was using to those new directories to find the data. If that isn’t feasible, for whatever reason, then a symbolic link from /home/Photos to /data/Photos will work seamlessly in most cases.

As far as I’m concerned, after administering enterprise systems using Unix going as far back as the early 90’s, symbolic links are a key tool in managing disk space that you shouldn’t just dismiss because it’s “an unnecessary layer of complexity”. Having smaller, purpose designed, file systems allows you to manage them better. Sticking everything into /home is probably not the right answer for anyone.

Resizing partitons is often not necessary. Use a symbolic link to relocate a subdirectory to another file system. For 99% of use cases this is indistinguishable from expanding the partition.

I guess they figure that Linux users already know what they are doing when it comes to security.

Not saddest, just worst.

To explain for those not in Canada… It is usual in Canada for a job to start with a low level of PTO an then add a week every few years that you stay with the company. This usually is capped at 6 weeks.

You can, of course negotiate an amount of PTO when you accept a job. Someone coming into a more senior position wouldn’t expect to start with just two weeks of PTO.

Wait til the OP learns about the Easy Bake Oven.

20.5 in winter and 21.5 in the summer.

I call BS.

I’m Canadian and my parents immigrated here from England before I was born. I have a UK passport as well as a Canadian passport.

I’m not English-Canadian, I’m just Canadian. No one hyphenates in Canada, and you cannot say that Canada has any more unifying cultural heritage than the USA.

Petrichor?

In the very first real programmer job that had, back in 1986, the IT department estimated that they had a 51 man-year backlog of development work. That would have translated to two or three calendar years of work. Probably more, considering how crappy estimates always are, and the always under-estimate.

It turns out that this is pretty much the industry standard. Virtually ever place I worked for the next 35 years had a similar size of backlog. And that backlog isn’t standing still, either. All you can hope is that 3 more years worth of new requests don’t come in during the two years it takes to complete what you already have.

Some of those new things are going to have a higher priority than stuff that’s already in the backlog. The reality is that some item that’s down at the low end of the list is going to get bumped down, again and again, and never get done. Or it’s going to someday become an urgent priority that can’t wait any more.

So the pressure is always intense for the developers to go faster, faster, faster. And the business doesn’t understand or care about good engineering practices, even though the shit hits the fan when a critical bug gets released to production. And God help you if that backlog of 51 man-years has grown to 70 after a year because of the technical debt you introduced trying to go faster.

The fight to rein in scope is constant. At that first job, the head of the department told us, “to build Volkswagens, not Cadillacs”. It was laughable, because they were struggling to keep up while building Skodas.

You can’t just add more programmers because the productive backbone of the development team is a group of programmers that have all been there for at least 5 years and they are domain experts. It’s going take at least 5 years to bring new hires up to that level of knowledge.

And that’s all three sides of the project triangle: scope/quality, resources and time. You can’t meaningfully add resources, scope’s already stripped down to bare bones and the time is too long.

And the truth is that every one of those projects in that 51 man-years backlog is important, even critical, to some aspect of the business. But the development process is unfathomable to muggles, so can’t you just go faster? Can’t you wring a bit more productivity out of those domain experts?

93= Four score and a baker’s dozen.

“My nipples explode with orgasmic delight”.

Proper pickled onions and Branston pickle.

Bob’s Red Mill makes an adequate substitute. It’s not as uniform as McCann, but it is good.

You are forgetting that other countries respond with tariffs of their own. Ultimately, the outcome balances out, just with higher prices for everyone. Local producers that rely on exports lose while those that sell locally win - as long as they don’t rely on imports for raw materials.

Consumers lose, especially on stuff that will never be produced locally, or rules on raw materials that can’t be sourced locally.

I used KDE Connect on Ubuntu with Gnome. No issues.

Old school Unix guy here…vi,awk and sed are all that you need.