[linesofcode]

A pre-commit hook that runs a linter and type-checking is absolutely vital to maintain the code formatting of AI generated commits.

One observation I’ve made working with LLMs is that sometimes it’s worth being flexible and conforming to the LLM’s code style and patterns.

Frankly the code doesn’t need to be elegant or follow arbitrary guidelines (in reality nobody cares if it uses spaces or tabs, what matters is the result).

In the past (pre-LLM) I used to nitpick people in code reviews, calling out a bunch of stylistic preferences that I believed would keep the codebase “consistent” and “elegant”. The idea was that if the codebase is uniform it’s easier for other engineers to iterate on it or debug.

Today I don’t care in the slightest.

I’m not the one writing the code nor am I the one actively debugging it, that has been delegated to the AI.

Furthermore very seldom am I actually reading any of the generated code unless it’s mission critical. I treat the code it generates as a black box until I can’t, and nowhere throughout that process do I worry about aesthetics.

Try to put aside all code vanity, accept that not all code will be aesthetically pleasing or elegantly written. Focus on delivering the end goal, not the syntactical minutia.