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

help-circle

  • Much the latter.

    Plus everything better work perfecly out of the box on any hardware, and there is a lot of different hardware. Compatibility layers are often built into the package.

    Java, for instance, recommenda that you package the whole (albeit slimmed down) JVM inside the package for the target platform, rather than relying on the java runtime installed already.

    The users arent expected to know any of that anymore.


















  • It’s actually the company’s problem. They usually opt to add more debt though, rather that wade through the old stuff.

    In the end, all software sucks and should be replaced as soon as possible. Code quality is a lie we tell ourselves so that we can sometimes be proud of our work. It’s usually the code we are most proud of that is the worst. Design patterns everywhere making the vode overly convoluted and “future proof”. The only future proofing that happens is that no-one will understand it, so they won’t change it. Trying to design for the future usually makes it harder in the future.