Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)HE
Posts
0
Comments
169
Joined
2 yr. ago

  • Because a lot of kids wouldn't watch the whole episode and think the first part is how they're supposed to behave... Kids don't have a very long attention span and caillous visuals were kinda odd. I remember feeling as a kid "These edges of the screen really take me out of the immersion", or at least the kid-equivalent of that feeling.

  • You make some great points. Using smaller functions and breaking up your code in readable bits makes a huge difference and you will likely never need comments if you do it right 👍🏻

  • Yes- exactly, they make comments wrong. But comments aren't always a waste of time, like in legacy code, or just in general code that isn't gonna change (mathematical equations too)

  • Fair. I guess in this case, it's a manner of gauging who you're working with. I'd much rather answer a question once in a while than over-comment (since refactors often make comments worthless and they're so easy to miss..), but if it's a regular occurrence, yeah it would get on my nerves. Read the fuckin name of the function! Or better yet go check out what the function does!

  • Yeah. I advocate for self explanatory code, but I definitely don't frown upon comments. Comments are super useful but soooo overused. I have coworkers that aren't that great that would definitely comment on the most basic if statements. That's why we have to push self explanatory code, because some beginners think they need to say:

     
        
    //prints to the console
    console.log("hello world");
    
      

    I think by my logic, comments are kind of an advanced level concept, lol. Like you shouldn't really start using comments often until you're writing some pretty complex code, or using a giant codebase.