AI - friend or foe?

Okay, hear me out. The V file is pretty straight forward and does what I want to do. I then can compile it to wasm and I have a web app. But originally I wanted to use web native stack (HTML+CSS+JS), but there’s a problem. When you inspect the loading_bars_demo.html (CSS and JS hardcoded), you’ll see I’m using two timers to do the job. The problem is, due to the web limitations (e.g. event loop), there’s a delay between the timers. In the file provided, the faster timer is offset, but it should perfectly match the slower timer. Can you rewrite my code, to only use one timer and not have this offset?

Right, the problem is, my example was just proof of concept (that failed). I need the solution to work for any combination of two “attack speeds”. And I will only know the “attack speed” at runtime…

This is a follow-up story to something simple. I was explaining my struggle to my programming guru and he said I gave up too soon and that JS is not as bad as I believe. I told him, I will try to rewrite the code using only one timer and if I can’t do it in an hour, I will disagree with him.

Fifteen minutes later, I was finished. Or maybe I should say, the AI was finished. You can see my prompts above. Now, there’s a lot of discussion whether AI will take over various CS disciplines. Here are my two cents. When I wrote the first version of the code, the AI was useless. But more importantly, even when it now can actually help you (sometimes), it does stupid things. When I got the revised code, I tried to test it and saw the problem is still there. Except it wasn’t, the bloody chat gipity set initial progress of both bars to 5. So despite it fixed the issue, upon copy-pasting the code, it looked like the issue is still there!

So there you have it. AI can only help you, if you can help yourself. If you have no idea what you’re doing, maybe you should think twice about making AI do it for you.