Kash Sajadi

I'm going to hazard a guess and say Claude just had a retraining. It's used "provenance" 5 times today. 0 times yesterday. No reason to pull thesaurus on me.

I have been a software developer since I was 14. I've been in this industry for 35+ years now, and in my opinion we software developers are some of the most arrogant people you can find around. If you talk to a plumber they know about plumbing and probably good with building things in general and perhaps DIY. They don't have any claims over genetics, music, space shuttles or other things. This is generally true for all professions except software developers. Most of us think we know everything: just go visit Hacker News and you'll see a bunch of overpaid, immature kids running around thinking they own the world. That was perhaps true for the past 20 years because we thought software developers is an art or special and different from other engineering deciplines. But now coding agents are proving us wrong and we don't like it.

"Use SES if you want low cost, use SendGrid/Postmark/Resend/Mailgun if you want sane ops" is a fake tradeoff. There should be a middle path: keep SES pricing without building your own reputation, suppression, and monitoring stack from scratch.

AWS gives you the primitives. It does not give you email ops. The moment you wire CloudWatch + SNS + Lambda + IAM around SES, you’ve started an internal tool you now own forever. That’s not leverage. That’s pager debt.

One underrated AWS advantage: email can stay in your stack. SES is easy to turn on. The hard part is everything after that - domains, DNS, reputation, bounces, complaints, suppression lists, alerts. Email on AWS is simple. Operating it isn't.

A lot of teams don’t leave SES because AWS is bad at email. They leave because SES tooling is bad. That creates a false choice: 1) migrate to SendGrid/Postmark/Resend/Mailgun 2) build your own control plane There should be a third option. SendOps is ours.

Hot take: don't switch email providers just because the dashboard is prettier. If you're already on AWS, SES is usually the right default. Keep delivery in your stack. Fix the operational gap separately. Infrastructure choice and dashboard quality are different problems.

This is what "When your product is great, it doesn't have to be good" means:

In a world where code is written by agents, having WYSIWYG editors for email makes no sense. That's why we built sendops.dev templates: From Git to your own SES account (+ everything you need to send emails!)

@markoa @twilio @gmail Ive been getting a couple of these every week for a couple of years now. No one at Twilio cares

the amount of phishing emails pretending to come from sendgrid is off the charts last few days hope @twilio will work with @gmail on addressing it

Markbase is like Notion, but for agents! markbase.cloud

I’ve got Markbase invites if you want one. I’ve been using it to share memory between Claude and Claude Code. It’s awesome. #claude markbase.cloud

Let me know if you are interested to try it out and I'll send you an invite: markbase.cloud

If you use multiple AI tools, we'd love to hear your feedback on Markbase. Markbase lets agents move context and memory across providers and tools, transparently. #ai #claude #openai

HackerNews has changed so much. These days it feels like a grumpy and hostile place full of trigger happy people ready to jump on anything that doesn't fit their narrow field of interests. It is sad to see it like this. @hackernews

What is the meaning of MVP in a world where you can just throw together a high-quality finished product in a week? #vibecoding #mvp #leanstartup

Isn’t it most ironic that the cold marketing subreddit has a no self promotion policy? Even spammers hate spamming.

I really want to pay @AnthropicAI to host my agents so I can build my SRE workflow there. Unfortunately, hosted agents with 98% uptime are not good enough for a casual weekend project, let alone an SRE workflow.

We used to get 1 or 2 vulnerability reports every month. Most of those were not very relevant. Now we get 1 or 2 every week. These are AI-generated, look very legitimate, but rarely have very valid disclosures in them. As a SOC2 Type 2 compliant company, we have to log every one of those reports, respond, investigate, and triage. The volume of work has just gone up. That's why we built Fortworx: An intelligent, security-focused spam filter for your security inbox. It accepts emails, monitors them, logs them, creates an audit trail, and assesses their validity, and responds automatically to the reporters with you as a human in the loop. fortworx.com #security #secops #cve