I’d agree with this, except they only really recorded a single album. The Rock n Roll Swindle was just a bunch of outtakes and session recordings mostly done after Johnny had left
I’d agree with this, except they only really recorded a single album. The Rock n Roll Swindle was just a bunch of outtakes and session recordings mostly done after Johnny had left
This is the most correct answer
Really good counterpoint, and you are correct, that I don’t know enough about it. I suspect that, like most things, there will emerge some real “power users” - the artists if you will. I think the problem that started this thread is that, currently, you see AI generated art everywhere and I do agree with that. Then again, maybe they said this about Cave art in antediluvian times…
I don’t consider it art. The only “creative” part is the prompt itself. Even then, it’s really just users trying to be as fanciful (or perverted) as possible. Once the prompt is ingested, the code takes its cues to remix the turgid crap that’s called the internet today.
Yes, once in a while it produces something “interesting” but this is an accident and not the desired outcome. Ask any artist about this - I’ve never met any that consider all their work as “good” (Ahem, Damien Hirst) and purposefully filter their own output. Ask AI to do that. It can’t. It will literally continue to shit things out until you ask it to stop. Again, like Damien Hirst…
The downside is it’s cheap and requires literally no skill. This means that soon, it will be pretty much everywhere, and thus we’ll continue the inexorable slide into abject mediocrity.
I’m not scared of the AI uprising. I’m scared it’s going to bore us all to death.
The tests help you discover what needs to be written, too. Honestly, I can’t imagine starting to write code unless I have at least a rough concept of what to write.
Maybe I’m being judgemental (I don’t mean to be) but what I am trying to say is that, in my experience, writing tests as you code has usually lead to the best outcomes and often the fastest delivery times.
This is why you write the test before the code. You write the test to make sure something fails, then you write the code to make it pass. Then you repeat this until all your behaviors are captured in code. It’s called TDD
But, full marks for writing tests in the first place
D’oh…