TheDoctor [they/them]

  • 2 Posts
  • 26 Comments
Joined 6 months ago
cake
Cake day: March 25th, 2024

help-circle






  • I often use comments as ways to say, “I know this is cursed, but here’s why the obvious solution won’t work.” Like so:

    /**
     * The column on this table is badly named, but
     * renaming it is going to require an audit of our
     * db instances because we used to create them
     * by hand and there are some inconsistencies
     * that referential integrity breaks. This method
     * just does some basic checks and translates the
     * model’s property to be more understandable.
     * See [#27267] for more info.
     */
    

    Edit: to answer your question more directly, the “why not what” advice is more about the intent of whether to write a comment or not in the first place rather than rephrasing the existing “what” style comments. What code is doing should be clear based on names of variables and functions. Why it’s doing that may be unclear, which is why you would write a comment.








  • TheDoctor [they/them]@hexbear.nettoScience Memes@mander.xyzVenus Fly Traps
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    1
    ·
    edit-2
    4 months ago

    Just a random guess, but I could see the argument that it would reduce crash bleed into the rest of the kit. It might make it easier to mix the main kit more tightly. But if that’s the case, then why leave the hihat low? It might just be a stylistic thing or it might be for the drummer to remember to not ride the crash. I dunno. It’s certainly not standard. They’re the only ones I’ve seen do it on such a small kit.

    Edit: I just realized it’s probably up so high so the drummer doesn’t accidentally kill their pollinators