Software Has Changed
abeautifulsite.net
abeautifulsite.net
To users of the software, no it doesn't really. Users only care about results aligned with their priorities.
That said, the act of creation changes the creator, so make sure that you are actually creating! The more you lean on LLMs to generate the concepts/ideas, the less "you" are creating them, and thus the less value to you as a creator the process offers.
Meaningful percentages of people already hate the obvious slop being thrown in their faces. The more they learn of the slop infecting the inside of the digital products they use—and the resulting enshittification—they will seek out worthy alternatives.
Sure but not everyone is as process driven, some are more outcome driven. Personally I care more about the outcome of your software (its quality) than I do the process you used to create it (LLM gen? transpired from some other language?).
Back in the day when I was into reversing MacOS apps (during the PowerPC era) there were these cross platform frameworks that were used sometimes that I really loathed. I did not like them because - Reversing: The binaries were a spaghetti garbage mess that (unintentionally) amounted to some serious obfuscation - User Experience: Ugly (no native elements), Slow (because of the aforementioned spaghetti), and Bloated (took up a lot of space back when that came at a premium)
The thing is though, I would not care if they had made these in Xcode Obj-C natively and just did a poor job of it. To me the end result was indigestible, and the process by which it was derived was neither here nor there. Even without LLMs, my world at that time was abound in generated slop that I did not like.
I think it's totally acceptable to be process driven. Much interest in art is based around the process or lived experience of the artist more than the art itself. I think it's mostly an aesthetic or cultural difference which side of the spectrum (if any) between process and outcome you live on.
Yes AI types it all faster, but I've lost the clarity and certainty of my understanding. I am finding I'm having to read the code deeply, but reading code isn't as fun or engaging as writing it.
And no, it doesn't matter how the end-product is made unless you care about maintenance/maintaining it.
Code in developed-environments (developed as in country) typically has an aestheticism to it. This served two purposes: beauty and comprehension. Comprehension and extensibility were tightly coupled before LLMs could "elaborate" endlessly. Now, extensibility and comprehensibility are only loosely coupled. But the ratio of people who have truly taken this to its maximum is not large. You still need good ideas and differentiating characteristics to make good applications.
It might seem like it doesn't matter which language or framework you choose, now that the LLMs can endlessly "elaborate." Since comprehensibility is largely optional now. But, if you desire extensibility, making thoughtful design decisions early , such as which language and which framework, can make a noticeable difference down-the-line.
It does matter if a coworker throws it away next week and replaces it with a fresh plate of slop, because generating code is just so cheap now.