Big PulseWatch update shipped ⚡️
Completely overhauled the UI across the landing page, dashboard, monitor pages and admin.
Also tightened up the boring-but-important stuff: CSRF protection, safer forms and better mobile accessibility.
Feels like a much stronger product now.
A developer apparently connected @claudeai Code to a 4-year-old Android TV and told it to sort out the bloat.
It disabled junk apps, changed animations, installed a lightweight launcher and made the TV faster than when it was new.
This might be my favourite genre of AI use: "this annoys me. Fix it."
What's the most mundane you've pointed AI at?
@madebydanl There’s stuff that I don’t want to bother ChatGPT with. Absolutely bonkers. Maybe I’m embarrassed to ask, for the 5th time, how long brown rice takes to cook.
Friday, beer o’clock. The jobs I care about most are the ones that will keep running after I close the laptop.
That’s the whole product thesis, really. Logs tell you when something explodes. They don’t tell you when it just… never started.
If you’ve got a script that should fire over the weekend, how do you actually know it did?
@AdemolaWealth_ This is totally what I’m trying to achieve…the silent stop. And it’s why I’m putting a monitor outside the thing that’s being monitored.
The failure mode nobody logs is the job that never started.
Logs catch exceptions. Cron “success” is often just silence. PulseWatch exists because I got tired of finding out three days later that a scraper had quietly stopped.
What’s the dumbest way one of your scripts has died without telling you?