| ▲ | zem 4 days ago | |
my advice for anyone in this situation - as the next step. work with claude to understand the context surrounding the change, and how it fits into the existing project. do a deeper dive into whether the change causes a performance regression, see if it's stylistically consistent with similar code, probe whether there is code duplication that you could clean up by pulling out a function. claude can absolutely help with all of this! and at the end of all that, read through the generated code with a fresh understanding of it, and see if you agree with how it was done or whether you might prefer anything to be changed. you will get a proper sense of ownership and of at least having put some work into not delivering slop, though of course there might still be subtle issues that only the people familiar with the codebase would catch. | ||