Two weeks turned into a habit. After the initial three week sprint where I built a Selenium + Ruby orchestration that replaced a repetitive, time sensitive manual workflow, I kept iterating. The result is a different way of thinking about browser automation that grew out of hard lessons with stale elements, fragile sleeps, and state races. I cannot publish the new implementation yet because it is still tightly coupled to the original project, but I wanted to share the core ideas and concrete patterns that have made the automation far more resilient and much easier to evolve.
