|
|
|
|
|
by dylan604
815 days ago
|
|
The hubris of any software dev is that code can do anything better. For a large majority of things, I would agree. After all, that's why we made computers in the first place. It's also my tenet of workflow automation. I'm not trying to eliminate a person's job. I'm just trying to make the tedious error prone parts of the job less tedious and error prone so that the person is free to spend more time on the things that they are good at and would be difficult to automate. |
|
I like to use Toyota as an example, because they famously reject total automation as a desirable goal. The believe having humans in the loop creates a learning loop that gets the best overall result, so they optimize for a sweet spot between automation and human.
To use an analogy from art, automation doesn't replace the artist, it replaces more limited paint brushes. As amazing as recent large model advances are, there's also a clear difference in how effective humans are at using them to get the desired result.
If you're just playing around then a simple prompt to finished image pipeline is convenient and shockingly good. If you're being more specific about the end goal then you need the model to expose more fine grained ways for the user to express what they want and modify the intermediate results. This why you see Adobe et all focusing on that kind of "smarter tool used in detail" approach.