|
|
|
|
|
|
by jaredcwhite
15 days ago
|
|
|
Only people actually do care about the process by which the products they use were created. It's our job, as experts who build things, to educate our audiences why and how we build what we build. 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.