Agree on the application side, but when it comes to the test suite, I'm definitely gonna consider letting an AI get that file started and then I'll run through, make sure the assertions are all what I would expect and refactor anything that needs it.

I've written countless tests in my career and I'm still gonna write countless more, but I'm glad I can at least spend less time on laborious repetition now and more time on the part of the job I actually enjoy which is actually solving problems.

Well I'm already a bad programmer, at least I save time /j

Preface: If all you want is to get a simple script/program going that will more or less work for your purposes, then I understand using AI to make it. But doing much more than this with it will not help you.

If you want to actually learn to code, then using AI to write code for you is a crutch. It's like trying to learn how to write an essay by having ChatGPT write the essays for you. If you want to use an API in your code, then you're setting yourself up for greater failure the more you depend on AI.

Case in point: if you want to make a module or script for Foundry VTT, then they explicitly tell you not to use AI, partly because the models available online have outdated information. In fact, training AI on their documentation is explicitly against the terms of service.

Even if you do this and avoid losing your license, you run a significant risk of getting unusable code because the AI hallucinated a function or method that doesn't actually exist. You will likely wind up spending more time scouting the documents for what you actually want to do than if you'd just done it yourself to begin with.

And if the code works perfectly now, there's no guarantee that it will work forever, or even in the medium term. The software and API receive updates regularly. If you don't know how to read the docs and write the code you need, you're screwed when something inevitably gets deprecated and removed. The more you depend on AI to write it for you, the less capable you'll be of debugging it down the line.

This begs the question: why would you do any of this if you wanted to make something using an API?

AI and the discussion around it doesn't live in a vacuum.

Occasionally you'll get shit opinions like this. Easy slutty greek frat bro strawmen that'll sleep with anything that moves and then dodge child support payments.

We all have to remember the true Chad argument against AI is that it's built on degenerate theft and corporate soulless shills. AI is the Shikrelli of creativity.

The same logic can explain why Teslas crash so often. You turn on all the assists, and eventually forget how to change gears.

I'd rather be a bad programmer that gets stuff done than a good programmer who's just jerking off about proper design

t. good programmer