As someone who's been on the hiring side there are some legalities involved on what to answer here. But I've always made a point of telling people who asked why. However I'm not in HR, so lots of people might get filtered before I even got a chance to interview them.

Also we asked candidates to do a take home and we talked about their solution during the interview, so most people got a good understanding of why they were rejected, but a couple of times people asked afterwards and I replied to them with the reasons we considered they were not at the level we were looking for, but that we would keep them in consideration for a more junior role if there ever was an opening.

Yes, but that's like saying "it's pretty standard for DE to have one minimize button, one maximize button and a close button". I chose clothes because they can't be standardized for the same reason as Linux, i.e. they're modular and people have different tastes on each of the modules, so the full thing can never be standardized even if some of the modules are quite similar among themselves.

Nope, Godot is open source, the current version can never become paid. If someone decided to make the next versions paid the community would just fork it and keep working on the free version. It's happened with some other projects in the past.

Nope, most people are fine with "I'm a programmer", the few times someone asked me what exactly did I program, I answered with the ELI5 version of what I do and that's always been enough, e.g.

• I make computers see and understand what they're seeing.
• You now site X? I work there
• You know game X? I work in the servers for it

I haven't finished the book, but I have to give it to the "Navidson record" in "House of leaves".

House of leaves is a book about a guy who finds a manuscript about a movie that doesn't exist. So there are multiple layers on the narrative, from near to far you have:

• The editor who's editing the book
• The writer of the book (Johnny) who tells his story and what he finds in the manuscript
• The person who wrote the manuscript (Zampano) and his views on the movie
• The documentary "The Navidson record" which the manuscript is describing. Filmed by Navidson (who's, as far as Johnny can tell, a fictional character in a fictional movie that never existed)

The reason why I have to give it to that particular piece of media within media is that everyone else in the book is a pain in the ass that feels that you have to drag yourself to in order to get to the next chapter of the Navidson record. So in a way it's a fictional media within a fictional media that's better than the fictional media it belongs to.

And in case you haven't heard of house of leaves, I'll leave you with a page from the book:

Same reason "clothes" cannot be considered standardized. Someone will think standard is jeans and T-shirt, for others it's a suit, and for others a dress, some will change clothes regularly, and others will only wear Nike shoes. If you try to define what everyone should wear you'll get people pissed off, and they will still wear what they want.

some religions don't follow the Gregorian calendar (such as Islam).

In fact no religion follows the Gregorian calendar, since that was invented by Pope Gregory in the XVI century, and by that time all of the major religions were already there. Christians migrated to the Gregorian calendar, but not everything, which is why Easter (which is also a Jewish holiday) keeps moving around on Gregorian dates.

Nope, it's a terrible one. Everyone will be constantly looking for new jobs. And would do the bate minimum to not get fired, that's the contract you're signing, bare minimum pay for bare minimum work.

Regardless of what you do, it's likely that you'll need multiple times the amount of employees to get shit done, because one dedicated employee is worth several doing bare minimum, depending on the job some works simply won't happen because no one gets paid enough to do them.

Besides that you'll suffer brain drain, i.e. anyone good enough will leave you, and they won't accept a raise to stay because if someone offered them double their salary and you tried to match it they would immediately see the bullshit you'd put them through and know that the only way to get a better pay again would be to get a new offer from someplace else.

Anyone bad enough that other companies don't want would be stuck with you, but there's a reason other companies don't want them.

You wouldn't be able to pull any new talent, you'd get stuck just getting people no one else wants because they're the only ones willing to work for that low.

• Put the gear in neutral (This prevents the car from trying to move when you turn the engine on)
• Press the clutch and the break fully (Same as above, also some cars won't turn on unless you fully press the clutch)
• Turn engine on
• Remove hand break
• Put car in first (or reverse)
• Slowly release the clutch until you feel the car is stable (this is not needed if the street is not inclined, or is inclined in the direction you want to go)
• Release the break
• Slowly release the clutch while slowly pressing the accelerator

This will be almost impossible. The short answer is that those pictures might be 95% similar but their binary data might be 100% different.

Long answer:

Images are essentially a long list of pixels, each pixel is 3 numbers for Red, Green and Blue (and optionally Alpha if you're dealing with a transparent image, but you're talking pictures so I'll ignore that). This is a simple but very stupid way to store the data of an image, because it's very likely that the image will use the same color in multiple places, so you can instead list all of the colors a image uses, and then represent the pixels as the number in that list, this makes images occupy a LOT less space. Some formats add to that, because your eye can't see the difference between two very close colors, they group all colors that are similar into one only color, making their list of colors used on the image WAY smaller, thus having the entire image be a LOT more compressed (but you might noticed we lost information in this step). Because of this it's possible that one image choose color X in position Y, while the other choose Z in position W, the binaries are now completely different, but an image comparison tool can tell you that color X and Z are similar enough to be the same, and they account for a given percentage of the image depending on the amount minimum of the values Y and W. But outside of image software, nothing else knows that these two completely different binaries are the same. If you hadn't loss data by compressing get images in the first place you could theoretically use data from different images to compress (but the results wouldn't be great, since even uncompressed images won't be as similar as you think), but images can be compressed a LOT more by losing unimportant data so the tradeoffs are not worth it, which is why JPEG is so ubiquitous nowadays.

All of that being said, a compression algorithm specifically designed for images could take advantage of this, but no general purpose compression can, and it's unlikely someone went to the trouble of building a compression for this specific case, when each image is already compressed there's little to be gained by writing something that takes colors from multiple images in consideration, needing to decide if an image is similar enough to be bundled in together with that group or not, etc. This is an interesting question, and I wouldn't br surprised to know that Google has one such algorithm to store all images you snap together that it can already know will be sequential. But for home NAS I think it's unlikely you'll find something.

Besides all of this, storage is cheap, just buy an extra disk and move over some files there, that's likely to be your best way forward anyways.