| ▲ | ac29 2 days ago | |||||||||||||||||||||||||||||||||||||
> What do you mean by "have it learn your conventions"? I'll give you an example: I use ruff to format my python code, which has an opinionated way of formatting certain things. After an initial formatting, Opus 4.5, without prompting, will write code in this same style so that the ruff formatter almost never has anything to do on new commits. Sonnet 4.5 is actually pretty good at this too. | ||||||||||||||||||||||||||||||||||||||
| ▲ | UncleMeat 2 days ago | parent [-] | |||||||||||||||||||||||||||||||||||||
Isn't this a meaningless example? Formatters already exist. Generating code that doesn't need to be formatted is exactly the same as generating code and then formatting it. I care about the norms in my codebase that can't be automatically enforced by machine. How is state managed? How are end-to-end tests written to minimize change detectors? When is it appropriate to log something? | ||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||