maintainability

Especially a maintainability rewrite just for the sake of maintainability.

And it's often vague when rules of maintainability pops up somewhere and people try to pick that up.

It follows the same philosophy: emphasis on readability, familiarity and maintainability, with PL research and new paradigms being non-goals.

Actually, there is a lot of evidence that maintainability is inversely related to the number of lines of code.

After all productivity and thereafter maintainability is really what is most important when building a product.

Use your experience to pick new tech that meaningfully improves UX, DX, maintainability or some other metric without creating problems.

The only thing that comes to mind is future maintainability when the code changes owners.

Indeed, but it could be argued that excess verbosity might be better for long-term maintainability.

If the code needs to live longer, initial speed becomes unimportant and maintainability takes over.

An outcome/engineering approach focusing on ends, not means (maintainability etc is a result, though logically secondary to the thing itself).

With a full-stack background, you have deep experience building and launching web and/or mobile products with an eye toward usability, maintainability, and robustness.

When creating apps which will be usen for maybe 10+ years using the most hip language or framework isn't so smart when considering maintainability.

From Tikhon Jelvis' answer: "I personally rank languages on three largely orthogonal axes: productivity, maintainability and performance.

I see it as trading maintainability for instant gratification." I agree and I want to add that for a language "with a bias towards system programming" C++ makes strange assumptions about the memory.

...is exactly the type of thinking that results is countless of wasted developer time wading through unmaintainable crap, which is never touched because "the code works" and everyone's to damn afraid to change it because it's so excessively complex because no-one bothered to go back and refactor it for readability, maintainability, modern libraries, or anything else.