cho.sh

2,244 notes

Liked on Xi'm obsessed about the smallest details https://t.co/2A4dA9xYptLiked on XAre you tired of bland writing? Add this prompt library! https://t.co/HLXPimt8at Funnier ◇ More persuasive ◇ Open-Source ◇ Up to 96% effective https://t.co/vQSUv7xESQLiked on XInstructions to get your CI under 2 minutes ⚡ https://t.co/GZzfvJsGIb https://t.co/vIqyh9enMHPosted on XThe server at https://t.co/HZRSCZTLdy sent back an error: 500 Internal Server Error @better_auth broLiked on XAnthropic just published an engineering guide on how to build always-on agents. The biggest misconception: an always-on agent does NOT run 24/7. It sleeps almost all day, wakes up for short runs, saves state, and goes back to sleep. The 5 core pieces I distilled: 1. Event Inbox Put a database table between webhooks and your agent. Acknowledge webhooks fast, run only one active worker per user so runs never collide, and batch rapid messages together. 2. Timers Keep timers in a separate table from the inbox. Split them into one-off follow-ups and recurring schedules. A background poller drops due timers into the inbox. 3. Lean Memory + Dreaming Only store what cannot be looked up again: user instructions, user notes, past messages, and task progress. Load a small index at wakeup, not every file. Run periodic dreaming passes to clean out stale facts. 4. Unattended Permissions Never put raw API keys inside the agent sandbox — inject them through an outside proxy. Use Deferred Tool Calls to pause risky actions for approval without blocking the worker. 5. Outbox Queue outgoing replies so your agent paces notifications instead of spamming users at 3 AM. https://t.co/1zew6WaRbEPosted on Xbro was so ahead of time https://t.co/hCT0GuJZJmReplied on X@xadisingh multiple reason should be multiple slack apps! like grok bot. It's the only gripe i hadLiked on XWe rebuilt our email API to Go. It took 7 weeks and 140 PRs, and we've been running in production for weeks at roughly half the median latency and one seventh the memory usage per task. Here's what it took to move our most critical API to Go 👇 https://t.co/WJzMVdoV7LLiked on XOur YC application video. Hollywood’s best are already using Shoty. We’re DoubleZero. We’re building a beast of an AI video model—not another API wrapper. @garrytan @ycombinator, good luck saying no. https://t.co/UXtOngpWTpReplied on X@ninjatofuture lmaoLiked on XBring some Y Combinator SUS friends to night life Taipei 🤘 https://t.co/cYZoyNObkALiked on X@anaclumos and this dudeLiked on X🇹🇼 My Top-Tier Taipei Spots — A Local’s Guide 🍸 Nightlife Xinyi * Barcode * Fake Sober * Ruff 🍜 Ningxia Night Market * Beans Village (豆花莊) — Jensen Huang’s favorite! * Yuen Huan Pien Oyster Omelette (圓環邊蚵仔煎) 🧋 Bubble Tea & Drinks * Dé Zhèng (得正) — Oolong tea with milk foam * Xing Fu Tang (幸福堂) — Brown sugar boba 🍚 Ximending * Tian Tian Li (天天利) — Braised pork rice 🥃 Taiwanese Spirits * Kinmen Kaoliang (金門高粱) — Taiwan’s iconic sorghum liquor. Look for vintage bottles from ROC years 80–90 (1991–2001). * Kavalan Whisky (噶瑪蘭) — World award-winning Taiwanese single malt whisky. 🏛️ Culture & Exploring * National Palace Museum (故宮博物院) * Dadaocheng & Dihua Street (大稻埕/迪化街) — Historic streets, local shops & traditional vibes. My DMs are open. Happy to show fellow founders around Taipei!Liked on XI made a mistake. When Jack and I decided to organize this $100K Hackathon, my biggest concern was cheating. Unlike a regular hackathon, everyone participates from home. And because the winner is whoever makes the most PROFIT (not revenue), there are so many ways to manipulate the numbers. So I added a $99 entry fee. One thing I’ve learned from building businesses is that people tend to be more committed when they pay for something. I thought it would filter out spam, attract serious builders, and make the competition fairer for everyone. But I completely missed the other side. 3 years ago, I was a living with my apps. Today, I’m financially free. My life changed so much that somewhere along the way, I lost perspective on what $99 means to someone else. For someone in India, someone struggling to pay their bills, or someone trying to make their first dollar online, $99 can be a lot of money. And those are exactly the people I want to help! I’ve spent years sharing what I’ve learned, reviewing random people’s landing pages, and organizing free meetups around the world. Not because there’s money to make, but because I genuinely love seeing people build things and succeed. And somehow, I was so focused on keeping cheaters out that I didn’t realize I was also keeping genuine builders out. That’s my mistake. So I’ve decided to make the $100K Hackathon completely FREE :) Everyone who already paid got a full refund. I’m still worried about cheating. That problem hasn’t disappeared, and Jack and I will have to figure out better ways to verify profits and keep the leaderboard fair. But that’s our problem to solve. Thank you to everyone who shared their thoughts. Sometimes you need people to remind you of things you’ve forgotten. I genuinely hope this hackathon changes someone’s life. ❤️Liked on XIt’s time to bring back Cafe CursorPosted on Xyo @pendev i can't live share edit a .pen file? it's the most needed featurePosted on XI'm coining a word "Agentsplaining" Agents condescendingly assuming the user don't know fuck and repeating the obviousReplied on X@jayhxmo @raycast Hard to explain. It's the small detailsPosted on X@raycast iOS keyboard is insanely good. Might resub Raycast pro just cuz of thisReplied on X@ishuagra02 I saw a theory that F5.2 is a post train of 5.1, but O5.5 is a distillation of F5.5(unreleased new pretrain) and thats why O5.5 > F5.2Liked on X@anaclumos don't know what is actually improved 👀Posted on Xam i the only one underimpressed with 5.2 fableReplied on X@bvvst great minds think alike https://t.co/YRFWhb1mcOLiked on XClaude Fable 5.2 is out and it's the perfect time to run this god-level prompt on your codebase: "I want you to audit our codebase, is anything here unnecessary, overly complicated in our current setup, or based on weak assumptions? Challenge them. - What can be deleted entirely? - What can be simplified now that unnecessary pieces are gone? Then make the changes. Prefer deleting over simplifying, simplifying over optimizing, and optimizing over automating. This product is being used by thousands of customers, do not cut any corners." This prompt is one I run often and leads to the best results.