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

help-circle




  • Writing good comments is an art form, and beginner programmers often struggle with it. They know comments mostly from their text books, where the comments explain what is happening to someone who doesn’t yet know programming, and nobody has told them yet that that is not at all a useful commenting style outside of education. So that’s how they use them. It usually ends up making the code harder to read, not easier.

    Later on, programmers will need to learn a few rules about comments, like:

    • Assume that whoever reads your code knows the programming language, the platform and the problem domain at least in general terms. You are not writing a teaching aid, you are writing presumably useful software.
    • Don’t comment the obvious. (Aside for documentation comments for function/method/class signatures)
    • Don’t comment what a line is doing. Instead, write your code, especially names for variables, constant, classes, functions methods and so on, so that they produce talking code that needs no comments. Reserve the “what” style comments for where that just isn’t possible.
    • Do comment the why. Tell the reader about your intentions and about big-picture issues. If an if-statement is hard to parse, write corresponding if clause in plain English on top of it.
    • In some cases, comment the “why not”, to keep maintenance programmers from falling in the same trap you already found.

  • I have been sort of following Wayland’s development for over 10 years now. I have been using Wayland for over 2 years now. I have been reading and watching various lengthy arguments online for and against it. I still don’t feel like I actually know it even is, not beyond some handwavey superficialities. Definitely not to the extent and depth I could understand what X11 was and how to actually work with it, troubleshoot it when necessary and achieve something slightly unusual with it. I feel like, these days, you are either getting superficial marketing materials, ELI5 approaches that seem to be suited at best to pacify a nosy child without giving them anything to actually work with, or reference manuals full of unexplained jargon for people who already know how it works and just need to look up some details now and then…

    Maybe I’m getting old. I used to like Linux because I could actually understand what was going on…





  • Floating Point Unit. The thing that does mathematical operations on floating point numbers. It used come separately from the CPU as an add-on chip, but around the 486 era, manufacturers started integrating it on the same die as the CPU. Of course, as these things go, from the system programmers point of view, there is still no difference between an add-on FPU and an integrated one.

    The one pictured here is an add-on FPU for an Intel 80386 CPU.










  • waigl@lemmy.worldtoMemes@lemmy.mlInvest in hwat?
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 months ago

    Top Left – More or less the default position, sensible enough, if a bit naive. Nothing wrong with this.

    Top Right – Having knowledge is a good thing, and so is making decisions based on sound risk-benefit analysis.

    Bottom Right – Well, at least it’s an informed decision. Just don’t try to pass off the risk on someone else if it backfires.

    Bottom Left – Oooouuuuh, you don’t want to be in this quadrant, trust me…