Industry: Construction (Iowa, US)
A schedule that copies itself, every day
A small service that logs into a web portal, reads the activity calendar and saves it to a database, recording every change.
The code is private and the client is described without their name.
The problem
A client publishes their activity calendar on a web portal with no export option. Catching a date change meant logging in, checking development by development and comparing against memory.
The system
- Once a day the service logs into the portal, the same way a person would.
- It reads the calendar month by month, across every development.
- It saves the activities to the database and flags the ones that moved or disappeared.
- Every change is logged with a date, so the history can be looked up anytime.
The result
- Checks every development each morning, without anyone logging in
- Every date change is saved with its full history
It’s the clearest example of what I do: a task someone did by hand, with a real chance of missing something, turned into something that just happens every morning.
Built with
- Python
- Supabase (PostgreSQL)
- Render