If you want to release details to a less than scrupulous company running an AI, you can feed it that information.
The real use is generating syntax. The logic is the hard part to teach, so with an understanding of the logic behind the programming, you can tweak variables for your final product.
I’ve mostly used this to generate scripts to deploy rapidly to the latest emerging crisis, but thats from the perspective of a help desk agent with too many years of experience to still be doing it, but in a way I enjoy it. The bigger problems aren’t my problems. I escalate as appropriate, and its no longer my problem.
I digress, it generates syntax and you plug in your infrastructure variables in a file you control. Then again I may be paranoid because I’ve seen HIPAA fuck extra hard with non-clinical staff who have access to records in their job duties.
Unit tests are exactly for code that is often rewritten, because it ensures that whatever interface still behaves the same, regardless of the implementation. This a large portion of the point of unit tests: not for testing the initial implementation but confirming that any subsequent implementation behaves the same.
In a normal scenario yes, but “vibe coding” rewrites whole swaths of code. It’s like painting detail with a bucket. Trying to keep up with it seems like a sisyphiean task
Using AI to write Unit tests is one of the few use cases I somewhat understand, but even that turns out horrible with improper supervision. I reviewed one Pull Request once where the testing was so horribly cobbled together and nonsensical that I rewrote those tests by hand (after asking the person I was reviewing to fix it twice and them only making it worse by letting their AI rewrite them)
The fallback is gonna be hilarious, the codebase rewrote by AI? With basically no considerations of business need and system capacity?
I can’t wait for the humiliating rollback
If you want to release details to a less than scrupulous company running an AI, you can feed it that information.
The real use is generating syntax. The logic is the hard part to teach, so with an understanding of the logic behind the programming, you can tweak variables for your final product.
I’ve mostly used this to generate scripts to deploy rapidly to the latest emerging crisis, but thats from the perspective of a help desk agent with too many years of experience to still be doing it, but in a way I enjoy it. The bigger problems aren’t my problems. I escalate as appropriate, and its no longer my problem.
I digress, it generates syntax and you plug in your infrastructure variables in a file you control. Then again I may be paranoid because I’ve seen HIPAA fuck extra hard with non-clinical staff who have access to records in their job duties.
I bet you their “10x coder” can’t describe what a unit test is nor its purpose
Then again, can you even unit test AI generated slop with how often it’s rewritten?
Unit tests are exactly for code that is often rewritten, because it ensures that whatever interface still behaves the same, regardless of the implementation. This a large portion of the point of unit tests: not for testing the initial implementation but confirming that any subsequent implementation behaves the same.
In a normal scenario yes, but “vibe coding” rewrites whole swaths of code. It’s like painting detail with a bucket. Trying to keep up with it seems like a sisyphiean task
Using AI to write Unit tests is one of the few use cases I somewhat understand, but even that turns out horrible with improper supervision. I reviewed one Pull Request once where the testing was so horribly cobbled together and nonsensical that I rewrote those tests by hand (after asking the person I was reviewing to fix it twice and them only making it worse by letting their AI rewrite them)