Vigge93

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

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

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

I mean, you just have to specify the format of the url that the search engine uses, and then the browser just formats in your search string into that. This has existed for years, if not over a decade, at this point, at least on desktop.

Now I imagine them just writing an incoherent string of words. "Tomato car house fireman oven duck garden rice..."

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

Why Friends? Just curious to hear you motivation