Pinned Tweet
Here is what I am building right now:
worththemath.com/
pivotgg.com/
mycomputerspot-security.beeh…
Calculators, security workflow stuff, and the cybersecurity newsletter.
Check them out and give me feedback!
Rust vs Go for AI agents is a fun fight, but measure where time actually goes first. If your agent spends most of its day waiting on model calls and tools, fast edit-test cycles and obvious failures matter more than a benchmark win.
Canva Craft is the trend today, but my test for any image generator is painfully small: can I fix one bad headline without changing the whole layout? A ten-second first draft is less exciting when every correction means starting over.
Cloudflare says some Workers Cron Triggers are late, skipped, or firing twice. Before retrying a job that sends emails or updates records, check what actually ran. If it fired twice, another manual run only makes cleanup worse.
MacBook upgrade chatter today has two very different headaches: local AI performance and storage that's already full. Figure out which one you've actually got before dropping Pro money.
A scheduled job that never started won't throw an error. I want the last successful run visible on the dashboard.
If the staff schedule changes, the booking page needs to stop offering those slots. A confirmation email won't help when the customer arrives and nobody's there.
Coding-agent rate limits have people rotating tools like shifts: one writes the PR, another reviews it. Fine. But I still want to know whether either one understood the task before I hit merge.
The backup dashboard can be green while the restore password sits in one person's password manager. Ask someone else to restore a file.
If Save gives no clear response, people click it again. Then there are two tickets. Show the result, and make the write safe to retry.
Seeing that resume-filter story everywhere. Before trusting an automated screen, run a few known-good resumes through it. If someone already doing the job fails, your 'efficiency' is just a very fast way to miss people.
A customer email can sit in a shared inbox marked read while everyone thinks someone else is answering it. Give it an owner and a due date.
Before rolling out passkeys, try the lost-phone ticket with your help desk. Find out what they require to reset access and whether the reset shows up in the audit log. Much easier to learn this with a test account.
Python is trending. My favorite use is still a tiny script that saves a small team from buying another SaaS subscription. But please, for the love of everyone on call, write down how to run it.
GitHub says Actions, Pages and webhooks are back. If you hit rerun while status updates were lagging, check what the first run actually did. Especially migrations. I wouldn't assume the first run did nothing.
githubstatus.com/incidents/8…
For a SaaS app, I want login monitored separately from the homepage. A green homepage check doesn't tell me whether users can get in. The alert should say where it failed: page load, auth response, or session creation.
Can anyone besides the owner get into your domain registrar account? I mean past 2FA, all the way to the renewal screen. I'd check that while the website still works.
AI Overviews are trending again. Show me the original site and label the ad clearly. I don't want to guess which part is an answer and which part paid to be there.
A 9 AM software outage at a small office can turn into two support calls that blame each other. I'd want one person on the vendor ticket, another checking the network, and a shared timeline of what's been tried. The office manager shouldn't have to be the message bus.
Saw a pitch this morning for an agent that 'automates IT operations.' Does that mean it summarizes alerts, or can it restart a service and close the ticket? I want the actual permissions list before turning it on.
