Finding signal on Twitter is more difficult than it used to be. We curate the best tweets on topics like AI, startups, and product development every weekday so you can focus on what matters.
How do we make codebases that are agent ready? At @aiDotEngineer, our CTO @EnoReyes breaks down why agents need tight verification loops to succeed, and why most codebases don’t provide those signals yet. Teams that invest in agent readiness will see 5–10× returns.
You can FINALLY switch between Opus 4.5/GPT-5.2 (or any other model) in the same chat in Droid I have been wanting this for a long time
2025 as an entrepreneur: Earned $885K with my startups Launched 3 new startups Built a $780K SaaS Made $147K in the stock market Got 107K followers on 𝕏 Read 10 books Traveled to 9 countries Exercised for 340+ days Gained 4kg of muscles Walked 4.2M steps Top 1% sleep score on WHOOP Reached 57.4 mg/kg/min VO₂ max Reached <18 yo biological age Drank 0L of alcohol Spent 365 days with my wife I hope 2026 unfolds like 2025: peace of mind, discipline, more startups. Happy New Year
My free 2026 Reset Challenge kicks off in just 1 week! You''ll get a short prompt each day for 3 weeks, where we identify a pattern to change and create a plan. 350+ ICs & EMs have signed up. I can''t wait to go through this challenge together! Join: modernleader.is 2026 Reset Challenge | The Modern Leader From modernleader.is
Here's how I'm coding with AI lately, might be helpful! 1. I write code primarily using agents, using models like Opus 4.5 and Codex Max for long-running tasks or tricky bugs, and Composer for frontend changes or fast updates (I still review the code). 2. Most of my web dev work happens inside the integrated Cursor browser. This is similar to using the Playwright or Chrome MCPs. Cursor can access network requests, console logs, and send elements on the page to the agent. It can also control the browser! Which can be fun for having it do automated testing: https://x.com/cursor_ai/status/199914795…… 3. I start projects pretty simple: no upfront rules, commands, or anything. As the project grows, I end up adding the most minimal versions needed. Some examples in this thread: https://x.com/leerob/status/200604326581…… 4. I heavily review all the code! Just because I'm using agents, I'm still thinking deeply about the architecture and code quality. I review the code in three passes: first, while the agent is generating it. Second, using the in-editor "agent review" before I push a PR (similar to a custom /code-review command). And finally, using Bugbot (AI code review) on my PRs. This combination helps me fix a lot of silly bugs before I ask other people to take a look at the code. 5. I always start new features with a plan (using Plan Mode). This helps significantly and I would highly recommend planning first regardless of what tool you use. I do like the Cursor UX for visualizing, editing, and saving the plans. You can view some of my plans here: https://github.com/leerob/pixo/tree/main…… 6. For really hard bugs, I use Debug Mode. It automatically instruments your app with logging, and then asks you to reproduce the issue. The agent then reads the logs and has much more helpful context to pinpoint the root cause. It also comes up with multiple theories on what the issue could be, and works through each one until it's fixed. Has been pretty helpful: https://x.com/cursor_ai/status/199882135…… 7. Always make sure you give coding agents verifiable outputs! They can't fix what they don't know about. For this, I would prefer using typed languages, and set up tools like linters and good tests. These are normal software engineering best practices, but they matter more than ever. There's also newer tools here like tsgo and biome/oxlint and bun which make dev really nice. Worth trying some of those if you do web dev. 8. I use Cursor from mobile! There's really two modes here: quick bug fixes or really big tasks. Quick bug fixes, I just pop open http://cursor.com/agents and fire away, knowing I'll get back a PR that will work 99% of the time and I can merge away. Easier than writing it down on a todo list, my PR queue is now that list. For big tasks, again I start with a plan and then I give the agent an ambitious goal (that is verifiable!). This allows the agent to run for much longer. It will keep going until it hits that goal, and if it gets lazy, you can just say "keep going" and go back to what you were doing. This is all in the cloud, in remote sandboxes, so I don't have to worry about my local machine. 9. Since someone will ask about the theme... yes I'm rocking light mode most of the time, using Cursor Light here Oh and if you're a car person... more on my car below soon
2026 is the GREATEST time to build a startup in 30 years I’m 36. I’ve sold 3 startups, helped build companies that raised billions, and backed teams from seed to unicorn. 20 MEGA shifts that make this the BEST time to build in a GENERATION: 1. Hardware got smart. Download open-source AI models from HuggingFace to cheap robots and they're suddenly smart. Opens up tons of use-cases. 2. SaaS is imploding. AI can replicate $500K software for pennies. Enterprise software that took 30 engineers now requires 1 and a Claude Code subscription. Founders will go more niche and more custom and outprice incumbents. 3. Outcome-based pricing is eating subscriptions. With AI agents handling work automatically, founders can guarantee results instead of selling features. This creates a massive arbitrage opportunity to steal market share from rigid subscription models. 4. Vibe marketing is the new marketing. AI agents/tools like Lindy, Gemini and Claude Code Using agents to do personalized outreach, ads and content creation it’s getting good. This is like getting on social in 2005. 5. Social is FYP-ified. Distribution no longer requires massive followings, just content that hits. Founders can build audience from zero without ads and then convert them to owned media channels (text/email). 6. Interfaces are vanishing. Conversations are replacing dashboards across industries. This removes training barriers and means customers can use sophisticated products immediately. 7. Companies are obsessed with efficiency and cutting costs right now. Corporate budgets are getting reallocated to AI. Companies are cutting traditional software spend to make room for AI-powered alternatives. This creates fast-tracked approvals for startups delivering 10x efficiency. 8. 99% of MVPs won't need VC. Low-cost MVPs combined with creator partnerships and AI automation allow bootstrapped scaling. For most software businesses, outside funding is now unnecessary. 9. Global teams. You don’t need to hire in your own city anymore. Opens up tons of arbitrage opportunities and ways to create products unlike before. 10. Millions of creators want to get paid. If you have the right product, the right network of creators, you can hit scale insanely efficiently. Never before did this exist. Next gen founders are building startups community first, software second. 11. Prototyping is nearly instant. With Lovable, Rork etc, you can test ideas in days, not months. MVP speed is basically 1x/week. This creates room for multiple products from small companies (multipreneurship), helps get to PMF faster, 12. LLM APIs create building blocks weekly. I can’t even keep up with how many new APIs/tools coming out from LLMs weekly. Example: Nano Banana pro comes out, probably 1000 ideas built on top of that can be $5M/year businesses. 13. $1m+ revenue per employee. With the leverage of LLMs, community and agents, employees are way more efficient. It won’t be uncommon to generate $1m per employee. This will lead to a rise of "multipreneurship", small teams owning multiple products /businesses. Holding companies will be as common as startups. 14. Superniche is the new niche. Because costs to create software startups is 1/100th, you can service little niches (i call them superniches) and still have a life-changing business. 15. Mobile app ecosystem about to 10X. 2 reasons. First is, adding AI to apps make apps more useful. More useful apps, make more money. Second, 16. Compliance and boring workflows are suddenly buildable. Permits, audits, insurance, payroll edge cases, filings, RFPs. These were “too annoying” for startups before. Agents thrive on rules, checklists, and repetition. The least sexy problems now have the best unit economics. 17. Claude Code killed the “engineering bottleneck.” The constraint is no longer “can we build it,” it’s “do we understand the workflow deeply enough.” The winning founders are ex-operators who encode tribal knowledge into agents. Code is cheap. Taste + domain insight is scarce. 18. The long tail of software is now profitable. Niches that capped at $200k ARR can clear $5M with near-zero marginal cost. 19. Services are quietly becoming software. Manual agencies are one agent away from product margins. 20. if AI can replicate $500K software for $20/month, what’s your moat? distribution, customer service, brand, data etc. REALLY good time to be a world class designer/marketer. (and even more.... but this is getting long already!) We've entered the rarest of windows... when multiple technological shifts collide at once, creating a brief period where small teams can build things that were previously impossible. THE FUTURE OF BUILDING STARTUPS IS DIFFERENT. I know this... This unique moment won't last forever. Markets will adapt. Giants will respond. The window will close. But right now, a founder with clear vision and bias for action can build more in six months than was previously possible in years. (note: if you need an idea to get creative juices flowing, grab one at @ideabrowser) The next generation of great companies is being created right now, many by founders you've never heard of. Some by people who would never have had a shot in previous cycles. That's the beauty of these rare windows. The playing field briefly levels, and the future belongs to those who see it clearly and move first. It's a sacred time, don't bookmark/share this, build something in 2026, will ya? Happy building, my friends. 2026 is yours. Am I wrong?
Feeling optimistic after my interview with @BillGates about health on @BBCr4today. "AI advances are the one reason that, even in the face of these aid cuts, I think we'll be able to continue to make huge progress." Full conversation at the 1:51:30 mark: https://bbc.com/audio/play/m002nv8b
BBC Audio | Today | Mustafa Suleyman Guest Edits Today
Trying to write more in 2026? I finally have an AI tool to recommend! It's the only thing I've tried that truly feels like a smart co-author. It writes in your style, has taste, and will even do research on your behalf. It's called @TrySpiral. Here's how it works
Here are my 2026 predictions for how AI will change software: - An agent-native software architecture. Most new software will just be Claude Code in a trench coat—new features are just buttons that activate prompts to an underlying general agent. - Designers get superpowers—and become superstars. When software is cheap to build, designers become powerful. They can finally make anything they want without waiting on engineers—and if you can make a beautiful experience you’ll stand out in a sea of vibe coded apps. - Agentic engineering becomes a new discipline. There is a new skill of software engineering emerging that is different from vibe coding and different from traditional engineering that uses AI. It is truly AI native engineering from professional developers who don’t ever look at or write code. They’ll be the most productive category of engineer in 2026, it will become a new discipline in itself. - AI training that indexes on sense of self. To achieve true autonomy, AI agents will need to run for long stretches of time without constant supervision—and to this end, we’ll see new training approaches that focus on giving agents their own sense of self, goals, and directions—we’ll start to hit the limits of people-pleasing, sycophantic AIs. Want more? I sat down with @every COO @bran_don_gell to trade our 2026 predictions and reflect on @every’s banner year. If you want to know what comes next watch below. Timestamps: Introduction: 00:01:05 Reflections on Every’s growth over the past year: 00:01:34 What changes when a company grows from 20 people to 50: 00:09:38 How “agent-native architecture” will change software in 2026: 00:11:55 Why designers are slated to become power users of AI: 00:17:13 The new kind of software engineer that will direct AI agents: 00:23:24 Why the next wave of AI training will focus on autonomy: 00:33:42
2025 has been an awesome year for Lovable. Here's what's top of mind for me right now: AGI will be a software system, not just a large language model. Over the coming year, there are only a few places in the world that can build this system. I started Lovable because I knew we had a chance to be one of them, and to ensure that when AGI exists, it's a world where human creativity remains important. For us to succeed, the thing I care most about is the team. How we work together. Inspire each other. Who we bring on. The problem we're solving has no playbook. Every week we're making decisions that have never been made, shipping things that have never existed. That requires people who can operate in uncertainty and move fast anyway. This is why we systematically hire people who can build something from nothing. Very often previous founders, who have run their own company and know what it feels like to make hard calls with incomplete information. To feel the weight of it and keep going. That instinct is hard to teach. I'm especially interested in people who are currently having the time of their life running their own company. That experience is exactly what's valuable as we build AGI here in Stockholm, with some some of the most exceptional and fun people to be around in the world. If you want to help, I'd love if you send me an email at founders@lovable.dev with who I should talk to. You're welcome to name yourself in the email. Ideally include 1-3 bullets on what they've been passionate about and what almost impossible things they've done. I'm excited to get to know you. Maybe partner or even work together.
🆕Apropos of completely nothing, here's the full 1.5 hour workshop from @ivanleomk introducing @ManusAI and the Manus API: https://youtu.be/xz0-brt56L8 Six ways to use Manus: - WEB APP: Full-stack applications with backends, databases, authentication, and Al capabilities. - API: Programmatic access to Manus capabilities for custom integrations and enterprise deployments. - MS 365 INTEGRATION: Brings Manus directly into Microsoft 365 with enterprise-grade security. - SLACK APP: Conversational bots that execute workflows. - BROWSER OPERATOR: Web automation tasks with persistent login state - MAIL MANUS: Processes newsletters and deep research workflows.
youtube.com
- YouTube
