Comment on Using AI to write better code more slowly by jrrembert

Great to see you come over to the dark side (re: AI coding)!Only thing I would add is to occasionally consider reviewer archetypes in terms of both their seniority level and "primary" role. I find myself increasingly reviewing code created by product managers, designers, and other traditionally low/no-code roles (including lawyers and marketers). It's often useful for me to review the code using a senior lens, but create the bug/explanation in language that they can both understand, and encourage them to learn.A verbatim example I used last week to explain Single Responsibility Principle:"Looks pretty good. You got it working, which is the hard part. One issue: this function is doing too many things which may make it easier to change later. It's kind of like mixing campaign strategy, copywriting, and reporting into one giant spreadsheet.

There’s a software idea called SOLID that gives names to this kind of thing (Single Responsibility Principle).

Next time, ask the AI: ‘Can you refactor this so each function or file has one clear responsibility?’"