• 0 Posts
  • 103 Comments
Joined 1 year ago
cake
Cake day: July 10th, 2024

help-circle
  • I don’t like code, that isn’t well documented. In fact, this has been my main source of frustration in the past and required the most time to deal with. Thousands of variables, hundreds of thousands of lines of code, how am I supposed to go through it somewhat fast, if there aren’t any comments or pieces of documentation that are guiding my understanding? I can’t spend half a year to just get a grasp of how the code works.

    Comments (as well as docstrings and readmes etc.) provide higher level overviews that can guide you through the code rather quickly, even if it may be longer in terms of words or character count than the lines of code it describes, it may accelerate understanding tremendously. It’s just a lot more effort to trace each variable and see what it does and how it interacts with others. This can quickly become exponentially hard to track.

    I don’t think it’s necessary to comment each line of code, except in rare cases or maybe when setting up a class and describing the members and roughly how they’re used, but a few words here and there, at some higher or intermediate level, roughly describing what you want to do, can go a long way for others (and even yourself, when working on a project for several years). It’s also already sufficient to just highlight the most important variables in a piece of code, when explaining it. Given that info, this steers your focus when reading the actual code.

    “Speaking” variable/function/… names are also very useful. I don’t care if it’s a long name, as long as it’s sufficiently expressive. E.g. “space_info” instead of “si”. This helps to understand the code more quickly and reduces backtracking lookups, because you already forgot again what a specific variable does that you haven’t seen for a while. My rule of thumb for variable naming: As consice, short and “essence grasping” as possible, but as long as necessary.









  • It’s wise to not give a fuck about downvotes. They can’t hurt you. You can’t make it right for everyone. And that’s okay. Sometimes you say stuff that agrees with a couple of people. Sometimes you don’t. Questions included, as some might see those as a statement. You’re free to do the same. Isn’t democracy beautiful?








  • I don’t have the time right now to addeess all of this, but:
    Device interactions can be used to identify users, predict and manipulate their behaviour, contribute to further identification measures etc…

    Furthermore my point was that there are many reasons to be cautious about any type of data collection and processing. Saying a specific type would be ridiculous undermines the possible dangers stemming from this. Therefore I wouldn’t plainly discard these concerns.

    Even if, in this context, the transmission is not widely noticed, this doesn’t pose a universal guarantee, especially if this can be turned on on demand via backdoors, trojans or whatever. Even worse if the transmission can be hidden. (Less likely for very proficient users with extremely tight network monitoring & control, but that’s rarely the case.)