• 0 Posts
  • 52 Comments
Joined 1 year ago
cake
Cake day: June 24th, 2023

help-circle






    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.





  • 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








  • ITT: People misinterpreting the idea as “facts that your school taught wrong”, when it’s really saying, “things that have changed since you went to school” (either through a change in definition or by new research).

    E.g. If you went to school before the early 2000’s, you were taught that Pluto is a planet, while that is no longer true since it was recategorized in 2006.


  • Not the Doppler effect, as that only applies to moving objects, but instead the inverse square law, where the energy of the sound wave decreases by the square of the distance from the origin, since it spreads in a sphere with the energy being spread across the surface of the sphere, resulting in a very quick dropoff in the loudness.