
"La libertad es como la felicidad: nunca se llega. Nunca se tiene completa." —Pedro J. Gutiérrez (Animal tropical) http://t.co/hrLjGCNrGG

Cineasta de mentiras · Escritor frustrado · Software engineer

"La libertad es como la felicidad: nunca se llega. Nunca se tiene completa." —Pedro J. Gutiérrez (Animal tropical) http://t.co/hrLjGCNrGG

Making the most AI pilled company is the whole game: 1. make a second brain. one folder of markdown files on how you think, write and decide (obsidian) 2. talk to it. voice notes all day (wispr), and an agent files every fact, story and decision 3. make a company brain. customers, calls, numbers, pricing, playbooks, past decisions and why you made them 4. record every call and meeting (granola). the transcripts go straight into the brain 5. keep a facts file. true things about you and the company that agents are allowed to say. this kills made-up claims 6. keep a voice file. your 50 best posts, 20 you hate, and the words you never use 7. put all of it in git (github) so every change has a history 8. write one instruction file at the top (CLAUDE.md or AGENTS.md). read these files before any task, never overwrite, always date 9. give agents memory across sessions so they stop starting from zero (claude-mem, mem0) 10. pipe every data source into one warehouse your agents can query (airbyte → clickhouse). ads, analytics, CRM, payments 11. feed it data nobody else has. it's the only part a competitor can't download the skills 12. don't start from zero. install the good ones first (anthropics/skills, obra/superpowers, mattpocock/skills, addyosmani/agent-skills) 13. grab the marketing ones too (coreyhaines31/marketingskills, cody schneider's graphed skills for static ads and UGC, boringmarketing dot com skills) 14. map every workflow in the company and rank them by money made or saved 15. do each one once while talking out loud, and record it 16. have an agent turn the recording into a skill. when to use it, the steps, the checks, the mistakes to avoid 17. one skill per job. small and boring beats one giant prompt 18. connect your tools with MCPs so agents can act and not only advise (gmail, slack, stripe, linear, notion, posthog, supabase) 19. give agents a browser (browser-use, vercel agent-browser, claude in chrome) 20. give agents a computer of their own for the tools with no API (vercel agent-desktop, orgo) 21. give your best skills away in public. it's the new lead magnet the agents 22. run an orchestrator that never turns off (grok bot, openclaw, hermes). it manages one agent per project, and each of those runs its own sub-agents 23. use coding agents for the building (claude code, codex, cursor, t3, antigravity) 24. wrap them in a harness so they plan, test and remember (ECC, superpowers) 25. manage the whole fleet in one place (paperclip). every agent gets a job, a budget and a log 26. put the skills on triggers (n8n, scheduled tasks). daily, weekly, on every new lead, on every cancellation 27. route your models (openrouter). the expensive one plans and checks (fable 5.2, gemini 4 carbon), the cheap ones do the volume 28. cut the token bill. shorter outputs, smaller tool results (caveman) 29. run a local model for the data that can't leave your machine (gemma 4) 30. track cost per job. if a job costs more than it earns, fix it or kill it the factory 31. build the line. spec agent → builder agents in parallel (git worktrees) → test agent → reviewer agent → deploy (vercel, railway) 32. design goes through the same line (paper MCP), and a skill strips out anything that looks AI made (unslop) 33. every annoying task in the company becomes an internal tool by the end of the day 34. every customer request becomes a pull request before a human reads it (tstack for the PR workflow) 35. reviewer agents with a named bar. "would the best team in the world ship this?" reject until the answer is yes 36. keep 50 real cases with the right answer. rerun them every time a new model drops and switch to the winner 37. humans approve, own the outcome and talk to customers. that's the 10% you keep the loop 38. every finished job writes back to the brain. what worked, what failed, what to stop doing 39. support tickets, analytics and social comments flow in every night 40. every friday an agent rewrites the playbooks from the week's results, and you approve the diff 41. every month, rank everything by profit per human hour. kill one thing and double one thing the growth 42. research with agents before you spend a dollar (perplexity API, last30days skill) 43. outbound runs itself. find the leads, enrich, verify, send (apollo, million verifier, instantly, phantombuster) 44. send prospects finished work in place of a pitch 45. ads run on a loop. an agent writes the creative, publishes through the facebook ads API, kills the losers and scales the winners 46. agents make the creative too. images (nano banana), video (heygen, fal), voice (elevenlabs), music (lyria 3.5, suno) 47. turn every finished job into content. the story, the number, the prompt 48. every customer makes the brain smarter for the next one. that's your network effect 49. once it works, point it at a new niche. same agents, new context The models are the same for everyone but your context is the only part that's yours. Acquire as much of it as you can, as fast as you can. Build loops like this. This is the whole game, happy playing.

I’m in love with this sentence: “An inch of movement is better than a mile of intentions.”

Had a great chat with @joelhooks about @alchemy_run, @EffectTS_, @foldkit and how AI is making high discipline, rigorous programming techniques accessible to everyone.
what if you could literally fork any business? @samgoodwin89 explains how you and your agents will be doing just that with Alchemy and Effect glhf

deploying persistent agents like Openclaw or Dots pose a major challenge for enterprise IT agents are more like contractors than traditional saas software, able to take proactive actions in the background without human intervention they are capable of fulfilling entire job functions but they can also take misaligned actions and write arbitrary code with unintended consequences today, we are sharing some of the best practices we use to manage fleets of claws at @OpenAI developers.openai.com/blog/s…

cuando trabajás con agentes, hay varias formas de repartir y organizar el trabajo. estos 7 patrones aparecen bastante: 1) agent loop → un agente ejecuta una acción, observa el resultado y decide cómo seguir. 2) prompt chaining → el trabajo se divide en pasos: el resultado de uno es la entrada del siguiente. 3) routing → un pedido se dirige al modelo o agente más adecuado para resolverlo. 4) parallelization → varios agentes resuelven tareas independientes al mismo tiempo. 5) orchestrator-workers → un agente principal delega subtareas a otros agentes y reúne sus resultados. 6) evaluator-optimizer → un agente genera una solución y otro la revisa. el primero usa ese feedback para mejorarla. 7) handoffs → un agente le transfiere el control a otro, que queda a cargo de continuar la tarea. lo interesante es que podés combinarlos: uno reparte el trabajo, varios lo resuelven en paralelo y otro revisa el resultado.

Every time we have a new model, I run the same simple prompt on all my projects: "Read this entire project and find everything that’s broken, inconsistent, inefficient, or no longer needed. Fix what you’re sure about and list the rest for me to review." highly recommend trying

Self hosting Executor is as easy as sending Claude the prompt: "Help me get executor.sh self hosted on my tailnet" and it'll do the rest - lock down one location with all your accounts rather than N connections across Y providers
I'm sick of having to setup + auth MCP servers across multiple machines and harnesses Giving @RhysSullivan's Executor a shot - connect apps once and then access everything over a single (or multiple) MCP connection I've got mine self-hosted and only accessible on my tailscale tailnet

alchemy and effect have completely changed how i THINK about building software (with agents) in a deeply profound way honestly thought i was done caring about "frameworks" but I was wrong it's a beautiful combination that is so insanely relevant to this era of building
what if you could literally fork any business? @samgoodwin89 explains how you and your agents will be doing just that with Alchemy and Effect glhf

starting a Workers project from scratch for the first time in ages, wild how much stuff you need to remember to tell your agent to not do its default slop - effect - oxlint/oxfmt/dmmulroy/anti-slop - pnpm - latest LTS version of node - hono - cloudflare.config.ts - sandbox 1.0

I 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. ❤️
Higgsfield gave me $100,000 to realize my dream: A hackathon where participants build a real business, not just an app. So... Introducing The $100K Hackathon: 🏴☠️ SHIP-OR-DIE.COM/100K-HACKATH… 🏴☠️ It starts on November 16, and you'll have 30 days to build a startup and make it profitable. The prizes: 🥇 $100,000 🥈 iPhone Duo 🥉 MacBook Neo This is not a joke. The winner will get $100,000 in cash. To win, you must: 1. Start a completely new business on Nov 16 2. Build a digital product (SaaS, directory, etc.) 3. Make the most profit (not revenue) You can already register at $99. When the hackathon starts on Nov 16, you can still join for $149. I'm running this with my dear friend @jackfriks, and we'll manually review each potential winner to make sure everything holds up. See you on November 16, builders 🏴☠️🫡

Every agent is going to have to become an operating system Apps are the ultimate form of plugins / mcps / artifacts You should use executor.sh though so your apps come with you across agents
Introducing: Devin Apps Private, secure, sharable web applications running directly on Devin’s cloud computer. Devin Apps are designed to power your most ambitious internal tools, preview deployments, and extensions to Devin itself.

Introducing opencomputer.dev An open source, faster Devin alternative you can self-host 0:23 Why it's 3.3x faster 1:27 One VM is all you need 2:01 Fully self hostable 2:16 Faster + cheaper at scale 3:27 Durable + secure 3:51 Star us on GitHub!

grok bot is the BEST AI agent orchestrator right now and THIS is the best setup i’ve EVER seen youtu.be/1cWZ7Ekff6E?si=YkcM… it runs claude code for engineering and paper for design here is the FULL setup and how to copy it:
Introducing Grok Bot 1.0. AI teammates that work alongside your whole team. Share Bots, collaborate with them in Slack and Teams, invite them to meetings, and watch them learn and become more helpful.

What’s it gonna take for @mattpocockuk to find and try @alchemy_run? A course is one thing. A framework that codifies and streamlines the entire DX is another.
As expected, the thing that is blowing people's minds most in my course is not the agentic stuff. It's the DDD stuff - domain-driven design. Building a ubiquitous language, using it with the agent, and refactoring the code to use it. Just bonkers how good it is
