The answer says “any character” not “any characters”, so it is still correct.

I would use single x and y when they are meant to replace numbers, and multiple xx and yy when replacing text.

E.g.

• “We sold x books yesterday”
• “Did xx stop by yesterday and pick up the books?”

While there might be some truth to that, I don’t think MS 365 would qualify as “developed for the government.”

1. I imagine that the company would have the burden of proof that any of these criteria are fulfilled.

2. Third-party rights most likely refers to the use of third-party libraries, where the source code for those isn’t open source, and therefore can’t be disclosed, since they aren’t part of the government contract. Security concerns are probably things along the line of “Making this code open source would disclose classified information about our military capabilities” and such.

Switzerland are very good bureaucracy and I trust that they know how to make policies that actually stick.

As long as it’s maintained. Wrong documentation can often be worse than no documentation.

Comment should describe “why?”, not “how?”, or “what?”, and only when the “why?” is not intuitive.

The problem with comments arise when you update the code but not the comments. This leads to incorrect comments, which might do more harm than no comments at all.

E.g. Good comment: “This workaround is due to a bug in xyz”

Bad comment: “Set variable x to value y”

Note: this only concerns code comments, docstrings are still a good idea, as long as they are maintained

It literally says “and” on the second to last row

Not to be too pedantic, but Californium is Cf

Damn right, you’d miss the Pan Galactic Gargle Blaster drink before the dinner. Not ok.

Being able to handle it, and being able to handle it efficiently enough are two very distinct things. The hash method might be able to handle long strings, but it might take several seconds/minutes to process them, slowing down the application significantly. Imagine a malicious user being able to set a password with millions (or billions!) of characters.

Therefore, restricting it to a small, but still sufficiently big, number of characters might help prevent DoS-attacks without any notable reduction in security for regular users.

What happens on the next iteration when i = 2,147,483,647 for each of our loops?

Not quite the same, there’s a subtle but significant difference

for(int i = 1; i > 0; i++)

I spent way too long trying to figure out why the guy and the ice cream shop were flying, and how he would move horizontally in he air…