Not sure why good coverage wouldn't mitigate risk in a refactor...
My mantra whenever I'm working with AI is that I want it to know what "point b" looks like and be able to tell by itself whether it's gotten there...
If you have a working implementation, it sounds like you have a basis for automated tests to be written... once you have that (assuming that the tests are written to test the interface rather than the implementation), then it should be fairly direct to have an agent extract and decompose...
I believe the Jesus Jones song, "Right Here, Right Now" has become an ironic commentary on Gen X; in that brief moment in the 90's when we thought the nuclear sword of Damocles dangling over all of us had finally been cut down...
Not a great song, but one that expresses the zeitgeist in a pretty succinct way.
We thought that we were at the cusp of a new era... one where we could overcome the injustices of the past and author a future based on the best version of ourselves.
In the end, Gen X never even got a chance to start; we watched from the sidelines as geriatric Boomers clung (and still cling) to power -- leaving less and less of that (ever more naive) dream behind.
"Right here, right now,
there's no other place I'd rather be.
Right here, right now,
watching the world wake up from history."
The song hasn't aged well & has become a cloy reminder of that time and what we didn't become.
Personally, I find this aspect of the work somewhat profound.
My graveyard of projects and dreams stretches out behind me and I feel saddened to know that these articles representing portions of my life never achieved what I had hoped for them.
However, I've come to view my work like a mandala or some representation of our mortality itself; our works and our lives are temporary.
We can make the most of the brief moment that we have – whether that be through work or through parenting or through base jumping – whatever that may be for each of us, or we can choose to do nothing with that moment, knowing that it's ephemeral and will be gone soon anyway.
I choose to try making each day's the best code I have ever written; I want it to be "beautiful" and maintainable in spite of knowing that it will be refactored, deleted or decommissioned at some point.
Not sure why good coverage wouldn't mitigate risk in a refactor...
My mantra whenever I'm working with AI is that I want it to know what "point b" looks like and be able to tell by itself whether it's gotten there...
If you have a working implementation, it sounds like you have a basis for automated tests to be written... once you have that (assuming that the tests are written to test the interface rather than the implementation), then it should be fairly direct to have an agent extract and decompose...