26 ms·

One problem I have with "how to do X with AI" is that every situation is different. For example, I'm bumping Symfony projects from 3.1 to 8.1. There's a clear p

One problem I have with "how to do X with AI" is that every situation is different. For example, I'm bumping Symfony projects from 3.1 to 8.1. There's a clear path here - Follow the written up migration guides PER major version - test all routes, authorised, etc. You can even hand-curate these tests. some might return 200, some might return 302 - Maybe optionally start with writing a safety net so you do not need to do these test manually, have e.g. a PHPStan baseline, etc. You're done when the routes are e2e functionally working as intended. You could even use snapshot testing here. I do not need to look at the AI here. I can review the code at the end, but I do not need to manually approve stuff here, hence safety features are off.

user3939382 3mo ago
Have you tried rector?
embedding-shape 3mo ago
> One problem I have with "how to do X with AI" is that every situation is different It's less of a "problem" and more a "How to approach content on the internet". Everyone is writing things from one perspective (usually) while there is a wide-range of perspectives out there, and what works in one situation doesn't work in another. "software engineering" as a whole is basically figuring out what goes where, and when, then trying to ignore the rest. Then lots of company blog posts wants to lead you to believe there are silver bullets, solutions that apply for every scenario and case out there, which usually isn't true. So again, less of a "problem" and more of a "Some things work in some situation", like we've been dealing with forever in software engineering. It's not right, it's not wrong, just applied practically different in different situations, perfectly fine and normal.