• 1 Post
  • 19 Comments
Joined 11 months ago
cake
Cake day: August 4th, 2023

help-circle




  • But then I decided, I wrote my own solution, a thing of 1,600 lines of code, which is, yeah, it’s like thousands of times less than the competition.

    And it works. It’s very popular. … I got 100 emails from people saying that it’s so nice that someone wrote a small piece of software that is robust, does not have dependencies, you know how it works.

    But the depressing thing is, some of the security people in the field, they thought it was a lovely challenge to audit my 1,600 lines of code. And they were very welcome to do that, of course. And they found three major vulnerabilities in there.

    He makes a ton of excellent points, but the succinct impact of this little example really hit for me. As someone who often rewrites things so that I can both understand and fully trust in what I’m depending on, it’s always good to be reminded that you literally can’t write 500 lines of code without a good chance of introducing a major vulnerability.

    The tech stack is so dizzyingly high today, and with so many interlocking parts, it continually amazes me that anything at all functions even in the absence of hostile actors.







  • Software devs for a long time would discuss “green field” development, which is a metaphor from constructing a building in an empty field: you start from nothing, and build all new. Most software devs prefer to write new code rather than try to learn the quirks and nuances of a large, already-existing pile of code, so “green field” is considered both desirable and often practically unattainable.

    “Blue sky” is a similar concept but loftier. It isn’t just that you have an empty field waiting for you, you’ve got the infitie expanse of the clear blue sky: endless possibilities, unlimited creativity, etc. “Blue sky development” as a metaphor I think comes from designers, product managers, and other software-dev adjacent fields. It means thinking of ideas that are out of the box and unconstrained by historical limits.

    That’s why everything is named that: execs and marketers love that kind of hollow promise. That anything is possible even though actually they’re almost always just clones of existing things whose greatest innovation is to loudly proclaim how new and innovative you are.


  • In the “Veins of the Earth” underdark setting for retro D&D, the author was clearly annoyed about this because they draw attention to the fine distinction between “Dark Vision” (which only monsters have) and “Infrared” or “Low Light” vision, which still give you some advantages underground but which both also require some kind of light source to work still.





  • Codex@lemmy.worldtoRPGMemes @ttrpg.networkThat damn armor
    link
    fedilink
    arrow-up
    8
    arrow-down
    3
    ·
    7 months ago

    I hate group checks for this kind of thing. I mainly only use them for perception or knowledge checks (always fun when one person is oblivious). For group tests like stealth or athletics for a chase it’s probably better to either build a challenge out of it so other skills can apply and more checks balance the luck factor, or just let one player be skill leader and make the check with appropriate penalties if part of their challenge is managing the clanky loud orc in plate.


  • “Come on everyone, we have to solve this riddle! What if the missing Scepter of Glorificon is in there?”

    “No we have to turn back! The lich ghost of the octo-king could be waiting for us, seeking revenge after we defeated him in his aquatic lair beyond time!”

    “GM, I ask the old sage NPC if they know what’s past the riddle.”

    Me, furiously scribbling notes and scratching things out: “Oh uh, they laugh heartily at your comments about the lich ghost. ‘Hohoho, the octo-king back so soon, that’s just ridiculous! But I know not what is beyond the door, the ancient prophicies say it is both what you most fear and desire…’”