top 50 comments

sorted by: hot top controversial new old
[–] 274 points 2 years ago* (5 children)

They did it once by mixing meters and feets, and crashed the Mars lander.

Edit: looked it up, wasn't actually meters vs feet, but newton-seconds vs some American eagles per gun unit for force

  • source
  • hideshow 10 child comments
  • [–] 76 points 2 years ago (2 children)

    It's guns per eagle, get it right. What would eagles per gun even be?

  • source
  • parent
  • hideshow 4 child comments
  • [–] 30 points 2 years ago (1 child)

    it happened again with the Intuitive Machines lander that landed on the moon last week

  • source
  • parent
  • hideshow 2 child comments
  • [+] 53 points 2 years ago* (last edited 1 month ago) (2 children)
  • [–] 13 points 2 years ago (1 child)
  • [–] 79 points 2 years ago (7 children)

    If a TODO passes code review, more than one person fucked up.

  • source
  • hideshow 10 child comments
  • [–] 32 points 2 years ago (2 children)

    At my first job after university, we did releases every Friday evening. From 3-5pm, all you would see in the Slack channel was a flurry of everyone committing straight to master (with a bunch of merge conflict commits between). Oh and then we'd release. Fun times.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 17 points 2 years ago

    A free for all, late Friday deployment is baffling… We’ve got a strict window of Tuesday-Thursday for releases (unless it’s a critical issue), and a 2-3 day merge freeze to help mitigate unexpected changes.

    We’ve got a relatively small team with LOTS of moving parts, so minimizing deployment issues is always top of mind.

  • source
  • parent
  • [–] 23 points 2 years ago (1 child)

    Eh, then you just get those idiots who avoid using TODO: because it makes the code review "harder".

    // This is a broken example.
    // Note: remove X before doing Y
    
  • source
  • parent
  • hideshow 2 child comments
  • load more comments (4 replies)
    [–] 78 points 2 years ago (2 children)

    I feel like modern compilers would turn their nose up at that shit. "Dead code? Ewww! No way I'm letting that into my syntax tree!"

  • source
  • hideshow 4 child comments
  • [–] 72 points 2 years ago (2 children)

    A lot of IDEs would probably throw a warning about unreachable code.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 13 points 2 years ago (1 child)

    implying that any developer actually reads warnings

  • source
  • parent
  • hideshow 2 child comments
  • [–] 14 points 2 years ago* (1 child)

    most of my (rust) projects have zero (or maybe 1-2) warnings, unless I'm in the middle of working on a feature

  • source
  • parent
  • hideshow 2 child comments
  • [–] 24 points 2 years ago (7 children)

    First thing I do on my projects is enable warnings as errors and increase my warning levels when reasonable.

    Unfortunately, the same can't be said on the projects I work on at work. Drives me crazy that we get likes 300+ warnings whenever we run the app and that we can't change it because "they're just warnings*.

  • source
  • parent
  • hideshow 9 child comments
  • [–] 8 points 2 years ago (1 child)

    🤢 Good lord.

    Though, I say that as I was basically forced to accept code that was using something marked deprecated because it was unreasonable to refactoring the code in that project. And I know we're never going to change it unless it stops working. 😭 At least I marked it as an issue on the review.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 9 points 2 years ago

    Oh yeah, I'm genuinely about to hand-in my resignation as soon as I find another job over this kind of shit. I keep being told that the business is really trying to clean-up its act when it comes to coding practices, but they keep putting some of the most incompetent people I've ever worked with in charge of shit (because they do promotions based on years of experience instead of actual actionable experience). It's awful.

  • source
  • parent
  • load more comments (5 replies)
  • [–] 12 points 2 years ago (1 child)

    Guess what? Flight Software usually uses ancient proprietary compilers for specialized hardware running an RTOS, rip 😢

  • source
  • parent
  • hideshow 2 child comments
  • [–] 58 points 2 years ago (5 children)

    At my workplace, we have a lint rule that reports an error if @nocommit is anywhere in the file, plus a commit hook that blocks all commits with @nocommit anywhere in them. It works well and has saved me a few times.

    Works pretty well, except the lint rule and its associated tests have to do something like "@no"+"commit" to avoid triggering it,

  • source
  • hideshow 6 child comments
  • load more comments (4 replies)
    [–] 18 points 2 years ago (3 children)

    Dude looks like Hank and Dale had a baby.

  • source
  • hideshow 4 child comments
  • load more comments (2 replies)
    [–] 16 points 2 years ago (1 child)

    Isn't this pretty much what happened with the LIDAR on the most recent commercial moon lander?

  • source
  • hideshow 2 child comments
  • [–] 15 points 2 years ago (1 child)

    B-b-but it clearly says right there in the todo, that's good enough, r-r-right?!

  • source
  • hideshow 2 child comments
  • [–] 17 points 2 years ago (8 children)

    I mean, my IDE highlights all the TODO's in yellow. I don't know how we could possibly make it any less error prone.

  • source
  • parent
  • hideshow 9 child comments
  • load more comments (7 replies)
  • [–] 12 points 2 years ago (1 child)

    If anyone is interested there is a wonderful walk about one of the apollo flight computers

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    [–] 11 points 2 years ago

    This got a lot of compression over less than a couple of hours!

  • source
  • [–] 7 points 2 years ago (1 child)

    Anyone know the artist? Saw another one by them a couple days ago about brute force protection.

  • source
  • hideshow 2 child comments
  • [–] 7 points 2 years ago (1 child)

    They still have those control desks in modern missions?

  • source
  • hideshow 2 child comments
  • [–] 13 points 2 years ago (2 children)
  • [–] 6 points 2 years ago

    On the one hand: kind of sad since this isn't too far removed from some workplaces. The hardware and furniture could be sourced from any number of places.

    On the other: hot damn. We can get the same kit NASA uses at home. Welcome to the future.

  • source
  • parent
  • load more comments (1 reply)
  • [–] 7 points 2 years ago

    git blame

    Naomi Nagata

  • source
  • load more comments
    view more: next ›