• 1 Post
  • 120 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle



  • You often need to be pretty good at math. But not because you’re “doing math” to write the code.

    In real world software systems, you need to handle monitoring and alerting. To properly do this, you need to understand stats, rolling averages, percentiles, probability distributions, and significance testing. At least at a basic level. Enough to know how to recognize these problems and where to look when you run into them.

    For being a better coder, you need to understand mathematical logic, proofs, algebra/symbolic logic, etc in order to reason your way through tricky edge cases.

    To do AI/ML, you need to know a shitton of calculus and diff eqs, plus numerical algorithms concepts like numerical stability. This is kinda a niche (but rapidly growing) engineering field.

    The same thing about AI also applies to any other domain where the thing being computed is fundamentally a math or logic solution. This is somewhat common in backend engineering.

    I’m not “doing math” with pen and paper at work, but I do use all of these mathematical skills all. the. time.

    I am an SRE on a ML serving platform.







  • cbarrick@lemmy.worldtopics@lemmy.worldAccidental Focus
    link
    fedilink
    English
    arrow-up
    2
    ·
    6 months ago

    Phone cameras tend to ramp up the saturation.

    It gives the photo a more vibrant look, which many people prefer, at the expense of color accuracy.

    But generally with artistic photography, you’re going more for a style than for accuracy, so I wouldn’t say it’s always a bad thing (though sometimes it is).




  • \1. Many retro games were made for CRT TVs at 480p. Updating the graphics stack modern TVs is valuable, even if nothing else is changed.

    \2. All of my old consoles only have analog A/V outputs. And my TV only has one analog A/V input. The mess of adapter cables and swapping is annoying. I want the convenience of playing on a system that I already have plugged in.

    \3. I don’t even still have some of the consoles that play my favorite classic games, and getting retro hardware is sometimes difficult. Especially things like N64 controllers with good joysticks.

    Studios don’t need to do a full blown remake to solve these problems. But I’m also not going to say the Crash and Spyro remakes weren’t welcome. Nintendo’s Virtual Console emulators toe this line pretty well.

    But studios should still put in effort to make these classic games more accessible to modern audiences, and if that means a remake, that’s fine with me.

    (I’m mostly thinking about the GameCube/PS2 generation and earlier. I don’t see much value in remakes of the Wii/PS3 generation yet.)




  • cbarrick@lemmy.worldtoPython@programming.devNumPy 2.0.0 released
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    7 months ago

    Huh. This got me curious.

    Yes, I did just type a bare URL. Every mature markdown parser I’ve used turns this into a link, and appropriately handles trailing punctuation.

    So I went to the spec, and it’s explicitly called out that this is not an autolink. Autolinks must be explicitly surrounded with angle brackets <>.

    So yeah \shrug.

    https://spec.commonmark.org/0.31.2/#autolinks

    Edit to be clear: This means that both of our markdown parsers are wrong relative to the commonmark spec. But I’ll argue that if a parser is going to attempt to autolink this, then handling trailing punctuation is better than not.