Jarrod Payne

@TheMattBerman @openclaw @vishalojha_me @Meta ads

I run my meta ads with @openclaw for $0/month 😱 here's the system that runs autonomously: step 1: daily health check → social-cli (major shoutout to @vishalojha_me) wraps @Meta's marketing API (token refresh, pagination, rate limits all handled) → am I on track? what's running? who's winning? who's bleeding? any fatigue? → the same 5 questions I asked Ads Manager every morning for 20 years step 2: catch dying ads before CPA spikes → @OpenClaw pulls daily frequency by ad → frequency > 3.5 = audience is cooked, CTR is about to drop → this one signal saves more money than any dashboard step 3: auto-pause bleeders + shift budget to winners → CPA > 2.5x target for 48hrs? auto-pause. no hesitation. → ranks every campaign by efficiency. recommends shifting spend. → last fri it paused an $87 CPA campaign at 3am and scaled my best performer 30% step 4: write new ad copy from your winners → agent analyzes what's working (hooks, angles, CTAs) → generates variations based on the patterns in YOUR top performers → copy modeled on what already converts in your account. step 5: upload ads directly to your account → new creative + copy → live in @Meta Ads Manager → no more downloading, formatting, clicking through the upload flow → agent handles the entire publish cycle step 6: content concepts + morning brief → spots patterns across winners and suggests what to test next → delivers everything to Telegram, Slack, wherever you want it → 90 seconds to read. reply "approved." done. input: your ad account + your target CPA output: an AI that monitors, kills, scales, writes, AND uploads your ads dozens of hours in ad manager → 1 text message I packaged the entire system as the Meta Ads Kit. 5 @OpenClaw skills: - meta-ads (daily checks + auto-pause) - ad-creative-monitor (fatigue detection) - budget-optimizer (efficiency scoring + shift recs) - ad-copy-generator (writes variations from your winners) - ad-upload (publishes creative directly to your account) giving it away free. comment ADS + like + follow (must follow so i can DM)

@BrooksLybrand React Compiler support 🙏 github.com/remix-run/reac…

The team has been super busy shipping awesome new features to React Router ...however, we've let our issues balloon a bit. We're tackling that this week Feel free to link any (with reproductions) you really hope we take a look at soon 🧵

If we lived in an universe where the scale and scope of the issues were as large as they are today in the opposite direction (government way too small / underfunded / draconian austerity), I would be in favor of an effective president deputizing highly effective people to reverse engineer the issue in a transparent way. Yes 👍

POLL: I’ll start by saying that I’m a huge fan of what @elonmusk is trying to accomplish with #DOGE. If, however, the “E” in @DOGE stood for “expansion”, would you be comfortable with a member of the private sector having unprecedented access to billions of accounts and payments, to EXPAND the government?

@theo Curious if you used this: github.com/rphlmr/react-r… Would love to see details on rr / vite / hono integration as I just migrated to this stack as well with a custom server.

How long do you guys think it will take me to move T3 Chat from Next to Hono+Vite? Considering giving it a shot tonight

@devongovett Mind sharing the code?! Looks really nice.

Yoooo CSS view transitions are incredible! This is like 100 lines. Wild. 🤯

@DariusDale42 @DOGE “political theatre at best” is the part I disagree with here. Time will tell, but I believe DOGE will have significant positive impact.

I too am optimistic on @DOGE. I'm also a data-driven realist. America's overspending and undertaxing problems are too big for #DOGE to fix alone. We need Congress for real reform. And for that, we need American voters to look themselves in the mirror and say "no" to more handouts in the form of tax cuts and income subsidies. I agree that @DOGE is severely needed. But relative to the ENOURMOUS SIZE of the US' fiscal problems, it is political theatre at best. At worst, #DOGE represents a DANGEROUS DISTRACTION from the serious discussions I am getting dragged by @elonmusk fan boys for trying to get y'all to have. Thank God for people like @LukeGromen and me for using our platforms to educate the masses on these critical dynamics. I am tapping into this zeitgeist with the express intent of preventing the loss of US dollar hegemony, which would inevitably lead to #WW3. Millions will die if we don't get this right!

@BasedMikeLee Rand Paul

Who would you like to see as the next Senate Republican leader?

@FCAllianceGK It’s ours. I will DM you

@billsader1987 @AdamRackis What problems have you had with turborepo? Loving it so far, but curious where issues may arise 🧐

@AdamRackis Please don't let Vercel buy and ruin another platform, I can't forgive them for Turborepo

I've got a plan to revamp Next's image 1: Vercel buys TanStack Start💰 1a: Tanner throws a crazy Red Bull & Coca Cola bender 2: app dir stays the same: it's your goto for eCommerce 3: new tan dir is added for web apps: it's TanStack 4: pages dir is deprecated 5: Profit 🚀

@juristr @youyuxi Typical Node.js API servers aren’t often. I have one powered by vite-node. I’d characterize it as an almost good experience. Really hoping this receives a lot more attention sometime soon though as I really enjoy vite for client applications. 😀

@youyuxi the question by now is more "what is NOT powered by Vite" 😅

Which means it’s also powered by Vite 🤩

@kenwheeler LVP

if you were gonna finish a basement, what would you use for flooring

I suppose it depends heavily on how expensive the work is. It’s not that I can’t see use cases for allowing work to continue. It’s just that I can see use cases for cancellation as well. (Presumably you do as well). Also, I don’t believe “doesn’t really stop anything” is a good argument. First of all, with no server support, it stops everything that happens after cancellation on the client. With server support, it actually can stop server work that isn’t required.

@paynecodes @samselikoff @CharleSpencer2 since it doesn't really stop anything, you can also let it resolve so you can put it in the query cache and re-use it until it gets garbage collected. Doesn't really have much downsides 🤷‍♂️

Today I learned that query cancellation doesn't work with suspense because we never get the trigger that an observer unmounts as uSES subscriptions don't run when you suspend. This is gonna get tricky to solve. Might even be impossible

@samselikoff @TkDodo @CharleSpencer2 Is it not better to cancel work you no longer need to perform?

@TkDodo @CharleSpencer2 But why? Genuine question bc I'm curious how you're thinking about this problem

@robertmclaws @mjovanovictech If you cluster on DateCreated, is it necessary to periodically cluster the table manually? SELECT cron.schedule('cluster_my_table', '0 0 * * 0', 'CLUSTER my_table USING DateCreated'); **postgresql

@mjovanovictech There is actually a really easy way to solve the “slows down the database” problem that doesn’t require new code. Make the primary key NonClustered. Cluster on DateCreated with a default value of sysutcdatetime() instead. Test perf on millions of rows, nearly as fast as ints.

𝗦𝗵𝗼𝘂𝗹𝗱 𝘆𝗼𝘂 𝘀𝘁𝗼𝗽 𝘂𝘀𝗶𝗻𝗴 𝗨𝗨𝗜𝗗𝘀? UUIDs (Guid in C#) are widely used as unique identifiers in databases. UUIDs are random, which makes them popular in distributed systems. However, UUIDs have some drawbacks: 1. UUIDs slow down database inserts. Each insert must update the clustered index, a B+ tree. Because UUIDs are random, this is an expensive operation as it requires rebalancing the tree 2. Higher storage costs. A UUID is 128 bits long, and it's even longer if you store it in human-readable format as a string. So, let me introduce you to ULIDs. ULID attempts to solve the drawbacks of UUID. It's also 128-bit, so it's compatible with a UUID. However, unlike a UUID, ULIDs are sortable. The first 40 bits of a ULID represent a timestamp, making ULIDs monotonically increasing. There's a .NET package that implements the ULID spec, so you can start using it immediately. However, you'll need to write some code if you want ULID to work with popular ORMs. What do you think about ULIDs? --- Subscribe to my weekly newsletter to accelerate your .NET skills: milanjovanovic.tech/?utm_source=Tw…

@ryanflorence This works pretty much always using pnpm

My entire life I've tried this workflow: - edit package.json - npm install it never works. I have to: - edit package.json - rm -rf node_modules - rm package-lock.json - npm install Is "edit package.json then install" not a workflow that's supported?

For a man who correctly predicted most of the big disasters of the last twenty years, Ron Paul is remarkably humble.

@firatoezcan @mxstbr @GraphQL I’m curious to understand your point regarding transactions? What does GraphQL do differently that leads to needing to write your own transaction code?

@mxstbr @GraphQL No union inputs and I don't want to write my own transaction code and I don't want to throw it over the wire as a string

Why are you not using @GraphQL?

For the last year I’ve been working on enabling a better developer experience for building TypeScript GraphQL servers. Today I’m pleased to share Grats: jordaneldredge.com/blog/grats/

@hbthegreat_ @bunjavascript @jarredsumner Do you have a reference for this? As far as I’m aware bun doesn’t run next.js. According to the docs there are still node.js apis next relies on not implemented in bun. bun.sh/guides/ecosyst…

@jarredsumner thanks to the team for getting NestJs working with Bun. I've been able to make some excellent improvements to our stacks build times and run times 🚀

@webdevcody I can’t understand how this isn’t consensus.

I've used lambda and serverless to host my applications for a while now... but I'm having a change of heart. I like the idea of serverless, but often the tooling surrounding deploying your serverless applications is a giant time sink. Tools like Terrraform, CDK, SST, Serverless Framework help, BUT the moment you hit an edge case in either aws or with this tooling, you end up wasting days debugging shit, waiting on stuff to roll back, stuff not working on prod after deploying but it works locally, going cross eyed reading yaml files and cloudformation templates, sub par type safety with terraform, no great offline support which requires you wasting tons of time mocking and building your own local solutions, etc. I'm slowly starting to convince myself just running your api in a container is the most maintainable solution for all software projects and has always been the case since containerization became a thing. The only reason serverless feels good is because you're using a library that abstracts it all away; the moment that abstraction fails you, welcome to hell.