College Prof in the US, focus areas are Human-Computer Interaction, Cybersecurity, and Machine Learning

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

help-circle


  • Vivaldi has been my browser of choice for years as well. Fantastic product in my experience. I’ve sadly forced myself to start using firefox and librewolf in an attempt support alternatives to chromium based browsers. Firefox and co. are fine, but I’m still reaching for features and options from vivaldi that just don’t exist in firefox without a maze of incompatible and poorly maintained plugins.



  • Make sure to buy one with a dedicated button for each letter you want to use. Really, I would recommend something QWERTY just for standard compatibility.
    Scarastic jokes over, it literally doesn’t matter at all. Just look online for the cheapest keyboard with the features you want. Type on a cellphone touchscreen keyboard if you are so inclined. If you are typing so much that it really starts to hurt your finger joints or muscles, then you can maybe start to look at ergonomic keyboards and see if they’d be right for you. Beyond that, your time is better spent actually coding than worrying about the proper type of keyboard to use.


  • DaleGribble88@programming.devtoProgrammer Humor@programming.devBill is a pro grammer
    link
    fedilink
    English
    arrow-up
    18
    arrow-down
    2
    ·
    edit-2
    10 months ago

    I have such a love-hate relationship with that video. On the whole, I think that video is bad and should be taken down. The creator is arguing against a very specific type of commenting but is harassing comments in all forms. It even addresses as such with a 20 second blurb 2/3 of the way into video distinguishing between “documentation comments” - but doesn’t really provide any examples of what a good documentation comment is. Just a blurred mention of “something something Java Doc something something better code leads to better documentation” but doesn’t elaborate why.
    It’s a very devious problem in that I don’t feel like any particular claim in the video is wrong, but taken within the context of the average viewer, (I teach intro. comp. sci courses and students LOVE to send this video and similar articles to me for why they shouldn’t have to comment their spaghettified monstrosities), and the inconsistent use of comments vs. code duplication vs. documentation, the video seems problematic if not half-baked.
    In fairness, it is great advice for someone who has been working in the industry for 15 years and still applies for junior positions within the same company - but I can’t imagine that was the target audience for this video. In my experience, anyone who has been programming on a large-ish project for more than 6 months can reach the same conclusions as this video.