<ul data-eligibleForWebStory="false"><li>The author built a cloud-based automation system on Replit but faced limitations due to the platform not allowing 'sudo' for installing Playwright's browser dependencies.</li><li>The author then moved development to GitHub Codespaces to complete the process, which technically worked well, but encountered issues with a login modal that didn't cooperate.</li><li>Multiple manual workarounds were needed in the automation process, making it fragile. This led the author to realize that the automation wasn't worth it for the problem at hand.</li><li>The author learned the importance of scoping down projects, evaluating effort versus value, and understanding that quitting isn't failure but good product thinking, highlighting that it's okay to stop if something is no longer efficient.</li></ul>

When Automation Isn’t Worth It — and Why That’s Totally OK

Discover more