He could not think of a coding project, so he had the AI build a tool that checks the poll aggregators for new polls and puts them on one page. He now hears about new polls about five minutes sooner.
Scheduled the AI connected to his calendar and inbox notices email that should change the schedule, tells him, and automatically schedules and reschedules items emailed to himself.
Around Elmira and Corning, New York, event listings were scattered across library systems, a brewery site, a school app, chamber newsletters and Facebook, so people found out about things the day after. He had the AI build one page that checks 101 sources across three New York counties and part of northern Pennsylvania: 1,855 listings over the next 90 days, 1,767 events after duplicates are merged, about 250 in any week, at 159 venues. A cron job reruns it every six hours on cheap shared hosting, about 8,300 lines of PHP, and cancellations mostly handle themselves because an event disappears when its source stops listing it.
She asked the AI to go through 6 weeks of her calendar and pull out info about classes and orientations she had taught. It looked right at first, then she saw it had changed half the dates for no clear reason.
This one went wrong. See what happened before you try it.
Volunteered and built a cartography data pipeline with coding agents for an educator, integrating sources updated every few minutes so new maps appear within about 5 minutes on a low-powered machine.
The developer set a scheduled job in plain words: every weekday at 8:30, send events from all calendars plus emails needing a reply, in five lines or fewer. The first run arrived at 8:44 with an apology for the delay, covered all 16 calendars, removed duplicate events and listed private events by time only.
Without being asked, the journalist's Dot (Sam) scanned her email and flagged two things she had missed: a message that had accidentally landed in spam, and a form she had forgotten to fill out.
He uploads his own data and points the AI to specific sources and documents, with examples he made before to show the format he wants. The AI then builds the tables and graphics for his Education Rights Project, public pages on education rights and funding in US states, with policy briefs, slide decks and interactive widgets.
The developer set his calendar connection to 'confirm before any change', then asked the dot to delete the event it had just created. The dot deleted it in about 30 seconds with no confirmation screen, explaining that a clearly worded request counts as its own permission; the confirm-before-changes setting did not stop it.
This one went wrong. See what happened before you try it.