OpenEvenings and weekends, paced around a college calendar
Working sessions and reviews of the bot and its failures
Who it is for
Students and early professionals who can describe a boring task in steps. Comfort with careful checking matters more than a specific degree.
What you build
- A written process of a repetitive job, step by step
- A bot that runs the happy path without you watching every click
- An exception path and a log that says why a run stopped
Modules
01
Write the work before the bot
If you cannot list the clicks, you are not ready to automate them. We start on paper.
02
Build the straight path
Open, read, file. Selectors, inputs, and a result a person can check.
03
Break it on purpose
A missing date, a moved button, an empty folder. The bot must stop and say which one.
04
Hand over the log
Someone who did not build the bot should understand the last run. That is the review.
What changes for you
- You can walk someone through a failed run without shrugging
- You can tell a process that should stay human from one that should not
- You have a bot and a log to show, not a certificate standing in for the work