You’re ostensibly arguing the same thing I am though. Focusing on building the thing rather than designing the code to look pretty.

I haven't read the codebases in question but people were talking about spaghetti code, which would not be well-factored and would impede someone less talented from comprehending it or being able to change it effectively.

I guess I'm saying there are code quality concerns which do affect velocity/maintainability and then there are superficial and stylistic issues. The former aren't just about some kind of beauty standard, they're part of executing.

I don't think "ostensibly" means what you think it means.

But I can't guess what you meant.