Imaginary Problems Are the Root of Bad Software

Re:Imaginary Problems Are the Root of Bad Software by kylelahnakoski on Sunday June 18, 2023 @06:24PM (#36385155)

Minimal change, or minimal code? Refactoring code can make code smaller but depends on good testing. Applying minimal changes results in redundant and complicated code, but less likely to break existing functionality.

[ Parent | on HN ]

Re:Imaginary Problems Are the Root of Bad Software by sirsinsalot on Sunday June 18, 2023 @07:07PM (#36385469)

In the first instance, both. However, i'd take more code that was better reasoned and easily understood over less verbose code that was smaller for smaller sake.

In terms of minimal change, we refactor when there's a clear business case to permit taking on the risk. Otherwise, we make the most minimal, most stable, least risk change to the existing code even if that code isn't optimal/pretty/well-structured/has-errors/...

Like most other engineering in the world really.

[ Parent | on HN ]

Re:Imaginary Problems Are the Root of Bad Software by paulryanrogers on Sunday June 18, 2023 @09:38PM (#36386348)

IME this can be hard if built on a platform or dependencies one doesn't control, which is common at early stage companies.

Because often the dependencies require surfing latest, or close enough, versions to maintain a secure system or avoid stalls for jumping major versions. Sometimes even core languages and standard libraries may require staying at least near latest versions.

[ Parent | on HN ]

Re:Imaginary Problems Are the Root of Bad Software by sirsinsalot on Monday June 19, 2023 @04:44AM (#36388749)

This is true, but in our case all dependencies are vendored and frozen.

We _do_ have instances where target systems for deployment become ABI/API incompatible with the libraries, which is rare and happens roughly every 5 years.

The project was structured to put stability at the core, rather than being cutting edge.

[ Parent | on HN ]