maintainable

Concise and maintainable are antagonistic qualities, and so Erlang's designers sacrificed all the conciseness they could get away with.

Surely it'd be simpler, quicker, and more maintainable just to match /(\d{5})/ and filter out invalid codes after the fact?

My pet peeve is front-end tests that ask you to write maintainable code, but you're not allowed to use any libraries.

My intuition is that a Radix tree trie would make a lot more sense and is more maintainable than such a hack.

It will always be a challenge to create a team-maintainable codebase with it.

Maybe looking for certain things to be out of an expected/naturally maintainable range?

Then spend another few weeks on learning how to write clean, maintainable code.

--- In the end it's better to work on a (perhaps) less maintainable product that people use compared to a very maintainable product that no one uses.

And on top of that quality output can be far more maintainable.

Are their solutions more maintainable, robust and long lasting perhaps?

Although I have found that to be less maintainable if the configuration file changes.

Now that we are post-v1 I'm certainly hoping to replace kube-up with something more readable and maintainable (or at least start replacing it).

You won't at first, but after you've hired a few who could "talk the talk" but then can't actually write readable, maintainable, and in some cases working code, you'll reevaluate.

I think "code without tests" is a fine example of technical debt or legacy code, but using it as the definition of either disregards the importance of everything other than tests that goes into making systems maintainable.

Maintainable code base - If you worked with more than 4 engineers on a non-trivial product, you would understand the appeal of a Java code base.