y/eah, I here all the podcasters describing how they're building things; and when it comes to something like translating a package from one language to another and that package has tests, it's a meandering but fruitful adventure. Because, of course, when you can sane tests you can always loop through. I did this with a package dependency I had, and it got 90% of the way there, but then one of the tests I expanded upon just refused. It ended up seeming like it was just a failed dependency.

But where there are no tests, and you're the one defining whats correct, you're definitely encroaching on the slot machine hoping it'll spit out something faster than you could do it yourself.

Then there's some vague unease in whether spending the time to prompt will actuall result in a properly integrated software in a large existing code base with idiosyncratic code use.

Overall, I don't see the ROI business gets from forcing people into these tools; however, as an individual, it's definitely worth understanding what they can do. Mostly, I see the efficient copy/past/find/replace of existing code to be very good.