e.ev

The rest: batch management, campaign workflows, DNS auth (SPF, DKIM, DMARC), blacklist monitoring, real time dashboards. Stack: Next.js, TypeScript, Express.js, PostgreSQL, Redis, Docker, Postal MTA. /7

Bot click filtering. This is the big one. I ran the same campaigns through well known shared ESPs and through my own infra. The shared ESPs showed open rates about 2.5x higher. Turns out corporate mail servers (Microsoft ATP, Barracuda, Proofpoint) pre-scan every link and trigger fake opens before any human sees the email. Most ESPs count that as real engagement. My platform separates bot tracking from real human engagement. For B2B this changes everything because your segmentation and optimization should be based on real data, not inflated numbers. /6

Built my own email sending platform with Claude Been doing B2B email marketing for 9+ years. You know the drill. Shared ESPs, shared IPs, shared problems. Some random sender on your IP block gets blacklisted and suddenly your campaigns land in spam. You open a support ticket, they say “we’re looking into it.” Cool. So I built my own sending infrastructure. Took a completely different approach than I expected. /1

A single malicious GitHub issue title reportedly compromised 4,000 developer machines through AI coding workflows. The weak point was not model quality. It was trust boundaries and review discipline around tool execution. Automation amplifies both speed and mistakes.

@braddunlap Interesting take. I suspect TypeScript also benefits because typed repos make agent edits easier to verify and roll back in CI.

TypeScript just became the most-used language on GitHub. Not because of a framework trend. Because AI coding tools work better with types. GitHub calls it a "convenience loop." AI handles TypeScript with less friction, so more people use it, which creates more training data, which makes AI even better at it. Languages are now competing for AI compatibility, not just developer preference. That is a strange new world.

@THArrowOfApollo That throughput jump is impressive, but 272k leads per second sounds like pipeline throughput, not end to end enrichment with retries and provider limits. Would love to see p95 latency and error rate over a full 24h run.

We were Clay's largest user at one point in time, hitting their platform 17.3 million times per week. Last month we replaced them entirely with a $200/mo Claude Code subscription. I can't write code. Neither can James, my VP of Growth who built the replacement. Here's the full story. Clay is a GREAT product and I TRULY think most people should use it. But we hit their ceiling. 50,000 row limit per table. 12.5 million row cap per workspace. Tables that take days to actually delete. Clicking "run all" thousands of times and waiting days for things to clear out. So When you're processing millions of leads, all the above become the bottleneck of your entire business. James had never touched Claude Code before. Three weeks after learning it, he built our entire core system. With Clay, processing 1 million leads took 27 hours. And it would error out often enough that we would always have to plan on hitting the “run all rows” button again on 20+ clay tables. IYKYK but Our new system waterfall enriches 1 million leads in 5 seconds. 272,000 leads PER SECOND. AND On top of the core engine, we vibe coded a Google Maps scraper that pulls leads zip code by zip code across all 32,000 US zip codes. AND An AI lead finder that hits 95% contact match rates where Apollo gives you about 30%. AND Ad library scrapers for Google and LinkedIn. AND An AI campaign analysis system. AND An auto-refill system so clients never run out of leads mid-campaign. One we started building with Claude, we just couldn’t stop Now we have the data ready for clients sending 5 million emails a month within 1 week of signing the contract. I put together the full system blueprint -- every tool, the tech stack, a Clay vs custom comparison, and a 6-step playbook for building your own. Plus a video walkthrough where I show you the live system and how each tool actually works. Retweet or Reply CODE below and I'll DM it to you.

Wikipedia entered read-only mode after a mass admin account compromise. Even with strong infrastructure, identity is still a single point of failure. At internet scale, account security is reliability engineering.

What is your biggest bottleneck in AI-assisted work right now: generating options, evaluating quality, or shipping safely? Most teams I meet are not limited by tools. They are limited by decision clarity and review discipline.

@DeFiMinty Prompts help but they only work if you actually read what comes back. If you're not reviewing the generated code, those 20 prompts just gave you false confidence.

When vibe coding, you can't tell AI to make everything secure and expect it to catch everything. Here are 20 real security prompts for vibe coders.

@Forbes The editor was always just the scaffold. The real question is who decides whether what the agent built is actually the right thing.

On January 5, employees at Cursor returned from the holiday weekend to an all-hands meeting with a slide deck titled “War Time.” After becoming the hottest, fastest growing AI coding company, Cursor is confronting a new reality: developers may no longer need a code editor at all. Check out the full story: forbes.com/sites/annatong… (📸:  Kimberly White via Getty Images for Fortune Media)

@rohanpaul_ai Jevons paradox is real, but the demand spike isn't evenly distributed. What companies actually want is engineers who can supervise AI output, not just more people to write tickets.

Citadel Securities published this graph showing a strange phenomenon. Job postings for software engineers are actually seeing a massive spike. Classic example of the Jevons paradox. When AI makes coding cheaper, companies actually may need a lot more software engineers, not fewer. When software is cheaper to build, companies naturally want to build a lot more of it. Businesses are now putting software into industries and tools where it was simply too expensive before. --- Chart from citadelsecurities .com/news-and-insights/2026-global-intelligence-crisis/

@bigglesdev @SemiAnalysis_ The Co-Authored-By point is real. But whether it's 4% or 15%, the more interesting number is how many of those commits had a human actually read the diff before it merged.

4% of GitHub public commits are being authored by Claude Code right now. At the current trajectory, we believe that Claude Code will be 20%+ of all daily commits by the end of 2026. While you blinked, AI consumed all of software development.

@vercel_dev Removing discovery and setup friction is exactly where agent tooling should focus. The decision of which integration you actually need stays yours.

AI agents can now autonomously discover and install Marketplace integrations using the Vercel CLI. ▲ ~/ 𝚗𝚙𝚡 𝚜𝚔𝚒𝚕𝚕𝚜 𝚊𝚍𝚍 𝚟𝚎𝚛𝚌𝚎𝚕/𝚟𝚎𝚛𝚌𝚎𝚕 --𝚜𝚔𝚒𝚕𝚕 𝚟𝚎𝚛𝚌𝚎𝚕-𝚌𝚕𝚒 Install the CLI skill and ask your coding agent to integrate a Vercel Marketplace product.

@HarryStebbings Maintenance is real, that's the right argument. But it doesn't follow that software companies are safe, it means the surviving ones need fewer people to do that maintenance work.

It is BS that vibe coding will replace software companies... "People underestimate how hard it is to maintain software over time. It's very easy to create the first increment but to change it, adapt it over time, it takes a lot of effort to do that. Businesses have a core business operation they need to focus on. Having a dedicated person or a team vibe coding some apps is a huge cost. So vibe coding is amazing but I don't think it's going to disrupt software companies." @zzeran Love to hear your thoughts on this @antonosika @amasad @jasonlk @JaredSleeper @dharmesh @tobi

@arlanr @nozomioai Context quality is genuinely the missing layer for most coding agents. The challenge is that even with great retrieval, a human still needs to check whether the agent pulled the right context for this specific problem.

introducing @nozomioai v1. state of the art search and index API to reduce hallucinations in AI agents. use it inside any coding agent or power your own products (thread):

@justinskycak The debt is real. But calling it a Ponzi scheme implies no one can make it work, when the actual issue is skipping review of what you ship.

Pure vibe coding is a Ponzi scheme. Eventually, the technical debt comes due, and if you don't understand the foundations, you can't pay it off.