I bought a new door for my house recently. When the salesman asked what type handle/knob I wanted, I had a bit of an internal crisis. The one he said post people got seemed like it would create a Norman door, which I desperately wanted to avoid. I ended up getting a standard knob to avoid being the absolute lunatic who spent 6 hours debating the merits of various door handles, but had I been alone, I would have absolutely done that. I still feel like I made a mistake every time I look at my door.
I think the difference is AI images tend to create mush or impossible geometry. The ideas here where a minimal change to the design renders the item entirely unusable takes a fair bit of creativity.
"what if objects were actually designed for a bad user experience, instead of a good one? she recalled in a 2018 TED talk. That was my ‘eureka’ moment."
Or, she stumbled upon some article or the very Wikipedia page about it:
Well, bash offers vi and Emacs as editing modes. We're already covered on that front. Many of the parameters for ls are cryptic, making it awkward to use for anything other than routine tasks without referencing the man page. more is so limited that many people choose to use a program used to concatenation files (cat) as a file viewer. Those who don't want to reach for their mouse to use their terminal's scrollbar buffer will use less, since it does more than more. Don't bother parsing that last sentence with bison, unless you have a yacc to shave.
Feed all command output through AI to summarize the results instead of actually giving the results.
Results from ls would be a few sentences explaining the types of files in the directory. Add a -l on there and it will give you a general overview of the permissions and size of the files. Ex. “These are rather large files that are primarily, but not exclusively, limited to root.”
Results from cat would give a summary of the file. You’d get the same results, with some degree of randomness from more and less as well.
Using any command with sudo would provide the same type of results, but in all caps.
Trying to pipe commands together would be a slop multiplier.
I recommend this book to anyone remotely interested in design. Even today it is fantastic.
I never look at doors, without evaluating their usability, anymore.
The book was a gift and a curse.
That is an interesting point to bring up, because this type of "almost but not quite right" is exactly what AI seems to naturally create.
Or, she stumbled upon some article or the very Wikipedia page about it:
https://en.wikipedia.org/wiki/Chind%C5%8Dgu
on the bottom (both) WHY?
i also do this for ui and app logic: go to some Microslop service, they are all like these...sad but true
Emacs and/or vi, depending on your inclination, have text editors covered already, of course ;-)
Results from ls would be a few sentences explaining the types of files in the directory. Add a -l on there and it will give you a general overview of the permissions and size of the files. Ex. “These are rather large files that are primarily, but not exclusively, limited to root.”
Results from cat would give a summary of the file. You’d get the same results, with some degree of randomness from more and less as well.
Using any command with sudo would provide the same type of results, but in all caps.
Trying to pipe commands together would be a slop multiplier.
so linux is already there
In terms of usability, moving to FreeBSD from Linux is quite a positive experience. Pity that hardware and software support is limited on the BSDs.
For example, the inner water tank of a robotic vacuum.