• 1 Post
  • 455 Comments
Joined 2 years ago
cake
Cake day: June 30th, 2023

help-circle








  • 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.



  • No thank you. No need to transform a classic character and franchise into something they notably are not. Being cool and charismatic and smooth and whatnot, in other words essentially the polar opposite of the average Jesse Eisenberg character, is part of the core identity of the character itself. Change that and you don’t have Bond anymore. It’s a whole different character that shares the name for marketing purposes.

    Nobody’s stopping nobody from writing their own movie with their own original character who happens to be a weird neurotic psychopathic nerdy secret agent, though. No need to hijack a cinema classic for that.



  • 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.







  • Until the next update reenables it.

    Really the only OS that where hibernation and suspension works smooth enough for me has been MacOS so far. Windows wakes up the whole PC to do things. On Linux you get GPU related power state issues that cause weird things. On MacOS it has always “just worked” for me. Still not buying one though. Rather shut down my machine.