• 1 Post
  • 113 Comments
Joined 10 months ago
cake
Cake day: March 19th, 2024

help-circle





  • “Adds a and b”?

    Sure, not useful. Thats a what, not a why.

    “Combined value needed for these outputs”

    The “why”. Useful. Shows the purpose, and explains the context it may be used in.

    Assuming the “why” is known is the mistake - and one I see from junior and mid level, I dont care what language it is, its the same. Using refactoring code as an example, without context - the why - can cause problems. What may be more efficient for one resulting value being presented can cause issues for others (let’s say precision as an example of why it could be a problem). Failing to include why something is being done is usually what introduces these problems, someone misses a different context than what they are looking at, and that belongs in a comment.

    A comment on “why” isn’t just important - for any block of code - it is, IMO, a requirement. I have and will continue to respond with “add comments as to why and resubmit”.


  • That really depends.

    Especially for a function that may see use in a variety of scenarios.

    I’m going to be firmly against anyone suggesting against proper comments - which, I’m sorry, but you are by your own statement.

    Code will change for many, many, many reasons beyond just refactoring.

    Edit: and why it was refactored is important as well.

    There are just so many reasons, and yes, I will continue to be against this newer trend of “dont comment, make codes your comments”.

    All that is, is a great way to make your code harder to manage later. It doesnt take much effort to explain why you’re doing something.




  • “Some people do a bad job commenting and updating comments, so lets not do comments” is not an approach that works for me.

    Most of my code is at the prototype level. I’m concepting something out, usually paired with hardware.

    If someone can’t follow what I’m doing, its going to lead to problems. If a change happens to the hardware being controlled, code will not be good enough on its own.

    Rather than being accepting of bad commenting practice, make comments (and updating them properly) part of good practice. In my experience, It saves time in the long run and leads to better code at the end.






  • curbstickle@lemmy.dbzer0.comtoSelfhosted@lemmy.worldCan't relate at all.
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    18 days ago

    At least as far as my setup, yeah. Ive got 5th-10th gens, under high loads I’ll see a spike to 80+ watts, the highest is 170W but those have nvidia quadros in them.

    Edit: For gpio now I’ll just use an esp32 or something instead.

    My only pi usage these days is work stuff, and orangepi is supported there. In terms of arm, also Jetson, but that’s kind of outside the discussion here.






  • Hired a cop who used pi’s for surveillance tech, when people mentioned being uncomfortable, they were flippant, blocked people, etc. Gross behavior IMO.

    Pricing has made a complete shift from consumer friendly cheap boards over to pricing that can be beat by x86 hardware (even full blown cheap laptops).

    The foundation has changed, and I just dont support it. You can make your own call of course, this is just my decision.

    Edit: I should note, I hold grudges. For a loooooong time. I still dont forgive Apple for lying about a battery issue in an iPod mini being a board issue, just to give you an idea for how long I can be an asshole about things I don’t like.