After all, D is supported by GCC and Clang and continually being maintained, and if updates stopped coming at some point in the future, anyone who knew a bit of C / Java / insert language here could easily port it to their language of choice.

Meanwhile, its syntax is more expressive than many other compiled languages, the library is feature-rich and fairly tidy, and for me it's been a joy to use.

1. In some large businesses I've worked in, so many people have been hired that some systems and processes have wound up being controlled by entirely different people from the people who need them. So coordination between people and waiting for people who have little to no incentive to do the thing they're being asked to takes up a large part of the working day.

2. In other businesses, a large fraction, or even a large majority of the employees have had no discernible job except to talk and write about the job performed by the few people doing an actual job. So a lot of time in these businesses would be spent dodging meeting invitations, rejecting grand ideas about revolutionizing the business with AI on the blockchain, saying no to "if you could X, that'd be great" and generally reminding people that they're not in charge.

The great thing about these problems is that you're not very likely to have them in a small startup, but if you decide to grow the organization later, you'll need to be very vigilant about how you scale.

So if your purpose is to archive these files because they're worth keeping, buying a bigger disk may make even more sense.

To pick one example, if you go to 0°06'40.6"S 28°56'27.0"E (-0.111271, 28.940829) in Google Maps, it'll give the Open Location Code "VWQR+F8W Maipi, Democratic Republic of the Congo", or some variation thereof, depending on your local language.

The most significant bytes, "Maipi, Democratic Republic of the Congo", are obviously not a location code, but a place name, and thus cannot be decoded at all.

Moreover, if you go to OpenStreetMap and look up "Maipi", it returns three places in Indonesia, and none in DR Congo. So even using a location service plus the algorithm could land you on the wrong continent.

The "Open Location Code" is essentially only usable as a search key for Google Maps. "Go look it up on Google" isn't a location code, it's advertising.

In larger corporations, the programming is often much higher level, and consists more of stringing together libraries and frameworks and entire systems so that they fulfill a business purpose. Even simple programs can take hundreds of megabytes of memory and have tens or hundreds of dependencies beyond anyone's control.

If you want to keep practicing your algorithm skills, you might try something like https://projecteuler.net/ , which is very mathy, or https://checkio.org/ , which is a bit more user-friendly, and get some practice there. As for OS theory, there are always open-source operating systems one can contribute to, though I suspect many of them would consume a lot of a person's time.

Did you notice how you can't "decode" the code without looking it up on Google Maps? That's not a location code, that's just using Google Maps.

#2 is a well-known problem that a vast number of people have run into - You have to have a job to get a job. The best advice I can give here is that getting a job through someone you know tends to be the most effective way, having an online CV and having them call you sometimes works, and actually applying to jobs is usually a dead end, but not always.

#3 might mean that they would like you to do that job instead of the job you originally wanted, but they phrase it as something that would be in your interest, since that's what they learned to do in middle manager school. If the other job is more interesting and pays more, then fine, but what are the odds of that?