• 0 Posts
  • 150 Comments
Joined 2 years ago
cake
Cake day: June 30th, 2023

help-circle



  • herrvogel@lemmy.worldtomemes@lemmy.worldQuestion
    link
    fedilink
    arrow-up
    12
    ·
    6 days ago

    Afaik lidar doesn’t work very well for detecting highly reflective or highly transparent objects. It’s possible, but not very straight forward and depends on what else is sorta “in frame”. I’m not sure how well lidar would fare when pointed at a large mirror that takes up a rather large portion of its fov.

    Radar wouldn’t be bothered though.


  • It wasn’t based on the book at all. The book itself is a compilation of short stories, but the movie’s script wasn’t based on any of those. It was originally written as an original action script that had nothing to do with anything Asimov. The studio that agreed to produce it made the writers rename it to “I, Robot” and insert a bunch of Asimov sounding shit in there, like the 3 laws and some character names.








  • Mostly the latter. We don’t do any optimizations on our product whatsoever. Most important thing is to say yes to all the customers and add every single feature they want. Every sprint is spent adding and adding and adding to the code as much as we can and as quickly as we can. Not a single second is allotted to any discussion about performance or efficiency. Maybe when something breaks, but otherwise we keep piling on more crap at full speed non-stop. I have repeatedly been told “the fast way is the right way” followed by laughter. I was told to “merge this now” on multiple occasions even when I knew that the code was shit, and told the team as much. I am expected to write code now and think about it later.

    As you can expect, the codebase is a bloated nightmare. Slow as shit, bugs galore, ugly inconsistent UI, ENORMOUS memory use, waaaaaay too frequent DB access with a shit ton of duplicate requests that are each rather inefficient themselves. It is a rather complex piece of lab management software, but not so complex that it should be struggling to run on dedicated servers with 8 gigs of RAM. Yet it does.




  • The why is easy. As others said, the vast majority of error messages are entirely useless for you, the user, because there’s not a single thing you can possibly do to address it. What are you gonna do about a database connection issue, or bad cache, or broken Javascript? Nothing. So don’t worry about it. Besides people are less panicky when they see an oops rather than a stack trace or a cryptic error message.

    And don’t worry, people who know how to write up useful support tickets and bug reports know how to do it even when all they can see is an “oops”. Builtin browser dev tools will have information they can use to help the devs.