[beerpls]

“ I look for readable, maintainable code, and try to make sure the writer is doing appropriate testing. But whether or not it works and is correct, that's not my job, that's the developer's job.”

And I personally refuse to work with this style of workflow anymore

Does the code do what it needs? That’s objective and it either does or doesn’t. I can manage that kind of review.

Does the code look pretty enough? This is subjective and guarantees i’ll waste hours of my life every month bc someone else felt anxious/neurotic/masochistic and wanted to dump a chore on me.

No thanks, if you have style guidelines i’ll follow them. I’m not your whipping boy that will ask how high when you say jump.

[smokel]

This is a bit harsh.

The fact that something is subjective does not mean that it is useless.

IMHO, writing maintainable code requires a lot of experience, which one cannot expect from all junior developers. Requiring style guidelines for everything is a bit pedantic, and does not even make sense when you stride in to new territories. The latter is increasingly becoming the only part of software development where I would like to go.

If all code and requirements would be so objective and so simple, then I'm afraid you'll soon be replaced by an AI agent :)

[gilbetron]

Readability is not "prettiness", it's minimizing the effort as much as feasible to understand what the code is doing. I don't care what lines the braces are on.

[bnjm]

> Does the code look pretty enough?

‘…readable, maintainable [and tested]’, ie. if someone else needs to modify or remove this code in the future, will there be friction?