|
|
|
|
|
by hmokiguess
34 days ago
|
|
I am not sure I understand the time savings you're describing here. Do you mean you saved the "time to write prompt into the text input box" because you got to do that sooner from your phone rather than write down your idea and do it when you got back to your computer? Wouldn't you be doing the exact same thing had you been sitting at your computer when you had the idea? Perhaps the person who wrote that had the mindset of "when I am away from my work, I want to be disconnected and present with the world around me, this updates now makes it so that I now have an excuse to carry work with me" Maybe they're in a toxic/abusive work relationship where taking breaks is already difficult and this might lead to justifying working from your phone as "expected" My question to you is: what is wrong with moving a little slower? Is time to prompt an optimization of a real bottleneck? |
|
At least, that's how I code through my phone. But it does require some forethought in establishing your automated workflows. I'm at the point where my entire dev system has established templates for CI/CD so I can preview work in staging and production is still a manual step (obviously).