• 2 Posts
  • 10 Comments
Joined 1 year ago
cake
Cake day: March 4th, 2025

help-circle

  • Sure, that’s the theory. In practice code review often looks like this:

    • a quick glance to see if the code plausibly does what it claims for longer patches
    • A long argument about some stylistic choice for short patches

    In other words – people were barely reading merge requests before. Code reviews have limited effects as well. You won’t catch all bugs or see if it actually works just by looking at the code. Code reviews mainly serve to spread knowledge about the code among the team. The more code exists in a project, the harder it is to understand. You don’t want huge areas of code, that only one person has ever seen.

    Project managers don’t necessarily talk to angry customers directly. They might also choose to chase more features instead of allocating resources to fixing bugs. It depends on what the bosses prioritize. If they want AI and lots of new features, that‘s what they will get. Fixing bugs, improved stability, better performance, etc. are rarely the priority.







  • The short and bloodless battle could have been sold better. In a TNG episode someone (Worf) would have mentioned some ancient Klingon marital ritual of ritual combat. Even better when it’s a story from Klingon mythology. Then they could call a P‘Qouth and duke it out for a symbolic minute.

    Helping people by force to save them from death is something that’s often done IRL, e.g. evacuations, suicide watch. Saving endangered species is a goal of many people and countries today. Saving an extraterrestrial sapient species and culture against their will is an easy case to make.