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

help-circle

  • For dipping your toes into a new topic I think it’s perfectly fine. It helps to provide useful pointers for further “research” (in a sense that would meet your requirement) and also manages to provide mostly accurate overviews. But sure, to really dive into this, LLMs like ChatGPT and co. are just some low-level assistants at best and one should go through the material themselves.













  • It’s easy to try on that pair of shoes. Those ignorants should go ahead and try building a community, try creating a video with some genuine effort regarding its content and - especially - edit it in an appealing way.

    Heck, I was doing some Blender rendering for fun as a hobby and am occasionally recording some demo videos of a project I am working at for my supervisor. Sometimes it takes about two hours to edit a fucking 10 minute video. This is just a huge amount of work. No wonder any creator, who has reached a sufficient level of income, hires editors.


  • Meanwhile, I work in a straining job where I come home, my knees feel weak, my right ankle is aching like fuck, I am mentally drained, I barely can even put together a thought process that tells me I should even have breakfast while fighting the urge to sleep while I try to have a fraction of what constitutes as a life. As well as work in a place, where I am almost always on threat of being fired for something petty because my management feels they have to have a bone to pick with me by fucking around with me and being snarky while doing it.

    Why the fuck are you doing that to yourself? Get another job. It sounds highly unhealthy where you’re currently at.



  • 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.