Non-technical people shipping real tools
Stories of tradespeople, farmers, designers, PMs, family members and founders with no coding background building and using working software.
36%
Best tweets about No-Code
50 Best Tweets About No-Code (2026)
A curated collection of the sharpest, most-shared X posts about no-code—saved so you do not have to dig through the timeline yourself. Updated every two weeks.
Builders shipping real products without writing a line of backend code.
- Creators
- 45
- Updated
Original Xholic analysis
What 50 top No-Code posts reveal
A largely supportive conversation (78% supportive stance, 80% positive sentiment across 50 posts from 45 creators) about non-technical builders shipping working software via AI agents and app builders. Tutorials and stack lists carry the highest median scores among multi-post formats. A minority warns about security, testing, governance sprawl and the gap between working code and products users want. Freshness is modest: 18% of posts were published within 90 days.
- Dominant tone
- Positive
- Median score
- 12.1
- Leading format
- List
- Recent posts
- 18%
80% of posts
All-time engagement
24% of posts
Published in 90 days
Conversation map
The themes creators return to
From coding skill to product judgment
Arguments that building is now about knowing what to build, taste and direction, with debate over whether reading code still matters for top engineers.
28%
Prompt-driven build workflows
Practical how-tos for directing AI agents: writing specs and PRDs, plan files, iterating, screenshot references, skills, memory and testing loops.
24%
Recommended builder tech stacks
Curated lists of tools for building apps without backend code: Lovable, Supabase, Stripe, Vercel, Bubble, Rork, Clerk and similar starter stacks.
22%
Limits, risks and quality gaps
Cautions about security, testing, governance sprawl, vendor lock-in, setup friction, and the gap between shipped code and products users actually want.
20%
Internal tools and build-vs-buy
Teams building bespoke internal apps, dashboards and automations that replace spreadsheets and paid SaaS subscriptions.
14%
New AI app-builder launches
Announcements and breakdowns of new prompt-to-app platforms like Codex Sites, Canva Code 2.0, Google AI Studio, Goose and DeepSpace.
14%
No-code AI agents and automation
Visual drag-and-drop builders and workflow tools like n8n, Make and Zapier for creating agents and automated business processes.
12%
Tone and stance
SentimentPositive leads
Author postureSupportive leads
Performance benchmark
- Median likes
- 33
- Median reposts
- 4
- Median replies
- 8
- Median views
- 2.1K
Posts with media make up 54% of this collection. Their median all-time score is 16.7, compared with 5.73 for text-only posts.
Format mix
- List24% · score 22.4
- Opinion24% · score 4.37
- Story20% · score 6.97
- Announcement12% · score 4.45
Consensus and debate
Where creators agree, and where they do not
Shared view
Non-technical people are shipping real tools
The largest theme (36%, 18 tweets) collects stories of farmers, tradespeople, designers, PMs and family members building working software. Examples include a Hokkaido broccoli farmer's farm system, an agency's HR app replacing a £40/month platform, PMs shipping live apps, and plumbers, roofers and HVAC techs building niche products.
Shared view
The scarce skill shifts to product judgment
Many posts argue the job is now knowing what to build. Naval frames vibe coding as the new product management. Layton Gott says the lasting skill is knowing what to build and how to get it in front of people. Eric Djavid says he writes product specs to an AI rather than code.
Shared view
Specs, plans and iteration loops matter
Workflow posts converge on structure: start with a PRD or markdown spec, have agents write plan files, iterate one problem at a time, and add tests and git early. Vaishnavi's summary of a non-developer shipping 70K lines lists PRD first, tests from day one, and security basics before building.
Open debate
Does reading code still matter?
Alex Lieberman profiles a highly productive builder who never reads code and believes no humans should. Daniel Lemire counters that top engineers will keep reading code because it is how deep insight is built, and that chatting with Claude Code won't make a top 1% programmer. Beto says non-technical builders still need to understand how apps are built, maintained and deployed.
Open debate
No-code vs. working directly with code
Ronin shares a no-code stack but notes that in many cases working with code is still better, because no-code builders can leave gaps. Joe Speiser asks whether complex drag-and-drop flows just move code into a flowchart that still needs developers for debugging and guardrails.
Open debate
Shipping fast vs. building what users want
Optimism about speed meets cautions. Umair Shaikh mocks founders who polish UI without talking to anyone. Degen Sing distinguishes working code from working products. Kritarth Mittal says getting people to care is becoming harder. Russell Fradin warns that employee-built agents create a 'digital junk drawer'.
What performs
Patterns behind standout posts
Tutorials and lists post the top median scores
Tutorials carry the highest median all-time score among multi-post formats (50.524, 5 posts), followed by lists (22.39, 12 posts). Opinion posts, equally numerous at 12, have a median of just 4.37.
Tech-stack theme scores highest
The recommended tech stacks theme has the highest theme median score (23.977), versus 6.64 for limits and risks and 3.62 for no-code agents and automation. Alex Finn's stack list is the top outlier at 1367.36, 112.63x the median.
Media posts score higher than text
54% of posts (27) include media. Their median score is 16.693, versus 5.729 for text-only posts, though this gap is an association rather than proof of cause. Per-post media flags are not supplied; the two cited posts are examples that point readers to an infographic.
Outliers beyond stack lists
Beyond stack lists, outliers include Naval's essay (1325.42, 109.18x median), Alex Lieberman's builder profile (599.44), andrew chen's spreadsheet prediction (471.57, the sole prediction post) and GREG ISENBERG's Codex Sites guide (422.83).
Statistical standouts
- View standout post 1Score 1367.4 · 112.63× median
- View standout post 2Score 1325.4 · 109.18× median
- View standout post 3Score 599.4 · 49.38× median
- View standout post 4Score 471.6 · 38.84× median
- View standout post 5Score 422.8 · 34.83× median
Creator landscape
Who shapes this conversation
The five most represented creators account for 20% of the selected posts.
1. Vaishnavi
@_vmlops
2 posts
2. Jacob Klug
@Jacobsklug
2 posts
3. Shushant Lakhyani
@shushant_l
2 posts
4. The Jobfather ® 🇯🇲🇨🇦🇬🇧
@TheJobfather__
2 posts
5. Todd Saunders
@toddsaunders
2 posts
6. Umair Shaikh
@1Umairshaikh
1 post
Conversation is broadly distributed
45 creators produced 50 posts, and the top five placements account for a 20% share. No creator posted more than twice.
Jacob Klug leads two-post creators
Among creators with two posts, Jacob Klug has the highest median score (75.88). His posts are an agency tech-stack breakdown and an account of a one-person content business run with Claude Code.
Todd Saunders reframes trades builders
Todd Saunders (median 12.66) argues that tradespeople using Claude Code are domain-expert builders, not people learning to code, and compares them to Shopify merchants.
Since the previous snapshot
What changed since Aug 24, 2026
- 62% of the selected posts remained.
- The creator count changed by -1.
- The leading sentiment remained stable.
How this analysis was made
Themes, sentiment, stance, and post format are classified per tweet. All counts, shares, medians, creator concentration, freshness, and performance comparisons are then calculated directly from the published snapshot.
Xholic's all-time score compares engagement while accounting for reach, post age, and creator consistency. It is used for relative comparisons within this collection.
This report analyzes the exact 50-post snapshot shown below. AI identifies editorial categories and drafts explanations; all statistics are calculated from the snapshot, and every narrative claim is checked against cited posts before publication.
Best No-Code tweets
Top No-Code tweets from 45 creators
Ranked 01–50
- 01
@AlexFinn ·
Every app I vibe code has the tech stack below Easy for beginners and free to start If you've never built an app before, just paste this list into Codex or Claude Code and you'll be good to go: Web framework: NextJS Hosting: Vercel Database: Convex Auth: Clerk Payments: Stripe Styling: Tailwind AI: logic- OpenAI, creativity- Claude, cheap tasks- Gemini Flash 3 Emails: Resend Design apps with: GPT image gen 2 + Claude Design AI I use to build it all: Codex desktop app w/ GPT 5.5 Any questions let me know!
- 149Replies
- 105Reposts
- 1.7KLikes
- 104.2KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 02
@naval ·
Vibe Coding Is the New Product Management “There’s been a shift—a marked pronouncement in the last year and especially in the last few months—most pronounced by Claude Code, which is a specific model that has a coding engine in it, which is so good that I think now you have vibe coders, which are people who didn’t really code much or hadn’t coded in a long time, who are using essentially English as a programming language—as an input into this code bot—which can do end-to-end coding. Instead of just helping you debug things in the middle, you can describe an application that you want. You can have it lay out a plan, you can have it interview you for the plan. You can give it feedback along the way, and then it’ll chunk it up and will build all the scaffolding. It’ll download all the libraries and all the connectors and all the hooks, and it’ll start building your app and building test harnesses and testing it. And you can keep giving it feedback and debugging it by voice, saying, “This doesn’t work. That works. Change this. Change that,” and have it build you an entire working application without your having written a single line of code. For a large group of people who either don’t code anymore or never did, this is mind-blowing. This is taking them from idea space, and opinion space, and from taste directly into product. So that’s what I mean—product management has taken over coding. Vibe coding is the new product management. Instead of trying to manage a product or a bunch of engineers by telling them what to do, you’re now telling a computer what to do. And the computer is tireless. The computer is egoless, and it’ll just keep working. It’ll take feedback without getting offended. You can spin up multiple instances. It’ll work 24/7 and you can have it produce working output. What does that mean? Just like now anybody can make a video or anyone can make a podcast, anyone can now make an application. So we should expect to see a tsunami of applications. Not that we don’t have one already in the App Store, but it doesn’t even begin to compare to what we’re going to see. However, when you start drowning in these applications, does that necessarily mean that these are all going to get used or they’re competitive? No. I think it’s going to break into two kinds of things. First, the best application for a given use case still tends to win the entire category. When you have such a multiplicity of content, whether in videos or audio or music or applications, there’s no demand for average. Nobody wants the average thing. People want the best thing that does the job. So first of all, you just have more shots on goal. So there will be more of the best. There will be a lot more niches getting filled. You might have wanted an application for a very specific thing, like tracking lunar phases in a certain context, or a certain kind of personality test, or a very specific kind of video game that made you nostalgic for something. Before, the market just wasn’t large enough to justify the cost of an engineer coding away for a year or two. But now the best vibe coding app might be enough to scratch that itch or fill that slot. So a lot more niches will get filled, and as that happens, the tide will rise. The best applications—those engineers themselves are going to be much more leveraged. They’ll be able to add more features, fix more bugs, smooth out more of the edges. So the best applications will continue to get better. A lot more niches will get filled. And even individual niches—such as you want an app that’s just for your own very specific health tracking needs, or for your own very specific architectural layout or design—that app that could have never existed will now exist.”
Watch video- 411Replies
- 683Reposts
- 6KLikes
- 554.5KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 03
@businessbarista ·
One of the most productive engineers I know cannot read code. @mvanhorn is not an engineer by training. He co-founded June, has 44,000 GitHub stars, and got contributions merged into Go & Python. I had him build live for an hour & walk me through his process. My fav lessons & quotes from the convo: 1) He never reads code. He does not have an IDE installed. In his words, "I fundamentally believe that very soon no humans should ever write any code and that no humans should ever read any code." 2) Every project starts with the agent writing itself a plan.md file using Compound Engineering. Agents are lazy, he says, and the plan keeps them honest. He never reads the plan either. "Plans are for agents, you silly human." 3) His CLIs leave notes for themselves. Each run records what it learned in a markdown file, so the next run starts where the last one ended. He calls them self-healing. 4) His agent has an email address. From Telegram on his phone, he sends a task. It emails his Mac, authenticated, and the work starts while he is at his kids' soccer practice. 5) He feeds whole transcripts, not summaries. After a two-hour meeting with a Google Ventures researcher, his agent read the researcher's entire book, wrote itself a report on every chapter, and turned it all into a plan for his business. 6) Him yapping to his agents is like nerd ASMR. "Go agent go" is how he likes to finish telling the agent what to do. 7) How he thinks about this next chapter of building: "Every generation of tools moves the engineer's job up a level. The code was never the point. The problem was."
Watch video- 37Replies
- 48Reposts
- 760Likes
- 76.9KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 04
@andrewchen ·
prediction re the end of spreadsheets AI code gen means that anything that is currently modeled as a spreadsheet is better modeled in code. You get all the advantages of software - libraries, open source, AI, all the complexity and expressiveness. think about what spreadsheets actually are: they're business logic that's trapped in a grid. Pricing models, financial forecasts, inventory trackers, marketing attribution - these are all fundamentally *programs* that we've been writing in the worst possible IDE. No version control, no testing, no modularity. Just a fragile web of cell references that breaks when someone inserts a row. The only reason spreadsheets won is that the barrier to writing real software was too high. A finance analyst could learn =VLOOKUP in an afternoon but couldn't learn Python in a month. AI code gen flips that equation completely. Now the same analyst describes what they want in plain English, and gets a real application - with a database, a UI, error handling, the works. The marginal effort to go from "spreadsheet" to "software" just collapsed to near zero. this is a massive unlock. There are ~1 billion spreadsheet users worldwide. Most of them are building janky software without realizing it. When even 10% of those use cases migrate to actual code, you get an explosion of new micro-applications that look nothing like traditional software. Internal tools that used to live in a shared Google Sheet now become real products. The "shadow IT" spreadsheet that runs half the company's operations finally gets proper infrastructure. The interesting second-order effect: the spreadsheet was the great equalizer that let non-technical people build things. AI code gen is the *next* great equalizer, but the ceiling is 100x higher. We're about to see what happens when a billion knowledge workers can build real software.
- 442Replies
- 290Reposts
- 3.1KLikes
- 1.3MViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 05
@gregisenberg ·
EVERYTHING YOU NEED TO KNOW ABOUT CHATGPT'S "LOVABLE KILLER" CODEX SITES (in 25 mins): TLDR; the coolest part is that apps you build can update themselves autonomously 1. Codex Sites is not Replit or Lovable or Bolt. Those are great for one-prompting a full app. Codex Sites is for building apps that the agent keeps improving without you touching them. 2. Your personal website can update its own stats. Your internal dashboard can refresh its own data. Your product can add features while you sleep. The app is alive. 3. Start by invoking at-sites. Use realistic sample data. Always say "save for review, do not deploy." This unlocks building a real product, not a homepage. 4. Add persistent storage so the app remembers everything between visits. Without this it resets every time. Ask Codex to show you the data model before it builds. 5. Create safe actions. These are the specific things the agent is allowed to do to your app: add data, update cards, move things, score things. You define the boundaries. The agent operates within them. 6. Build skills so any future Codex chat knows how to interact with your app. The skill is basically a manual for the agent. Without it, every new chat starts from zero. 7. Save gate like a video game. Codex doesn't auto-save. Create checkpoints before you deploy so you can roll back if something breaks. 8. Close the autonomous loop. This is the magic. Once memory, safe actions, and skills are set up, the agent can update your app from any chat, any context, without you switching tabs. 9. Use the plugins most people are sleeping on. Figma, Canva, HeyGen for avatar videos, Game Studio for interactive experiences, FAL for image generation, Hugging Face for open source models. Worth adding a few. 10. The big picture: we went from building apps to raising apps. You set up the structure, the guardrails, and the skills. The agent does the rest. That's autonomous product building and it's here right now. Tbh, Codex sites isn't perfect. Still a lot to be desired like domains, db, authentication etc. But it's a glimpse into this idea that apps can be updated/improved upon automonously. And Codex Sites is REALLY good if you live in Codex everyday. Which more and more of are. And that's really cool. Will be interesting to see how Lovable, Bolt, Replit etc react to this. full tutorial on @startupideaspod where you get your pods https://t.co/vKRQL70Nds watch share with a friend i'm rooting for you What do you think of Codex and Codex sites?
Watch video- 67Replies
- 65Reposts
- 747Likes
- 68.5KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 06
@VaibhavSisinty ·
Man. Jack Dorsey just open-sourced an AI agent that builds entire projects from a single prompt. And it's completely free. 🤯 It's called Goose. You type "build me a website like YouTube" and it gets to work on its own. Creates the project, writes the code, installs dependencies, fixes errors, and keeps going until it's done. Works with 15+ AI providers Claude, ChatGPT, Gemini, Ollama, OpenRouter. Connects to 70+ tools through MCP. Desktop app, CLI, or API. Free forever. Private by default. Open-source to the core. The guy who built Twitter just gave away a tool that lets anyone build software with zero code. Ideas just became more valuable than technical skills.
- 19Replies
- 47Reposts
- 300Likes
- 19.6KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 07
@Jacobsklug ·
I run the #1 vibe coding agency. We've built 250+ apps for clients using AI. Here's the exact tech stack behind every build: 1/ @Lovable This is our main coding agent. It gets us off the ground faster than anything else. Great design out of the box. Backend and infrastructure setup from the jump. We go from idea to working prototype in hours, not weeks. Every client project starts here. 2/ Supabase This is our backend of choice. Database, APIs, security, and auth all in one platform. The real advantage? It's baked directly into Lovable. No extra config. No messy integrations. You connect it once and everything just works. For us it was the obvious choice. 3/ Claude Cowork Lovable handles basic testing on its own. But when you're shipping real products for real clients, you need more. PlayerZero lets us run advanced product cycle testing in one automated process. Fewer bugs. Faster QA. Clients never see a broken build. 4/ Stripe Every app we build that takes money runs through Stripe. Subscriptions, one time payments, invoicing. It plugs into Supabase cleanly and Lovable can scaffold the full checkout flow in minutes. Payments used to be the hardest part of shipping. Now it's one of the fastest. 5/ Mixpanel You can't improve what you don't measure. Mixpanel gives us event tracking, funnels, and retention data from day one. We wire it into every client app so they know exactly where users drop off and what's converting. Analytics isn't optional. It's how you prove the app works. This stack lets a small team ship at the speed of a 50 person dev shop. No bloated tools. No unnecessary complexity. Just five platforms that do the job. That's how you build software in 2026.
- 28Replies
- 20Reposts
- 203Likes
- 13.4KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 08
@alexcooldev ·
I always use vibe coding tools like Rork before I start coding. They help me map out ideas and app flows fast, like sketching the product with AI. No real code yet, but you already feel how the app looks and works. Here’s how I usually do it: 1) Use ChatGPT to generate a detailed prompt based on my idea or upload screenshots of competitor apps so it can write a precise, complete prompt. 2) Paste that prompt into Rork, let it generate the flow → refine the logic, add features (login, AI chat, etc.) 3) Once it feels right, export the code and continue vibe coding inside Cursor. Why I love it: > No need for Figma > Iterate ideas faster > Visualize the app flow before touching real code Build smart, not just hard.
- 25Replies
- 19Reposts
- 265Likes
- 20.3KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 09
@DeRonin_ ·
My tech stack for solo building (no-code): Framer – landing pages & websites Webflow – advanced site building Bubble – full web apps Airtable – database Zapier & n8n – automation Make – advanced workflows Stripe – payments Versel – deployment process for web apps Supabase – backend + auth + storage, all-in-one Tally – forms to be honest, I mostly use Claude Max, but there you usually have to work with code if you're just starting out, this stack will be more than enough but it really depends on how complex the thing you want to build is in many cases, working directly with code is still the better option no-code builders can leave gaps or not fully implement your idea that's the reality, but they're still very useful
- 31Replies
- 19Reposts
- 318Likes
- 31.9KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 10
@vivoplt ·
Vibe-coding tools you should know about • @claudeai - AI for coding + debugging • @cursor_ai - AI code editor • @Replit - cloud coding + instant deployment (mobile app) • @vercel - hosting • @github - AI coding assistant • @NanoBanana - Image generation • @midjourney - More image options beyond NanoBanana • @rainbowdotme - Web3 wallet connections • @RevenueCat - For subscriptions • @Lovable - AI app and website builder • @rork - For mobile apps • @Dribbble - For design discovery • @v0 - UI component generator • @zeddotdev - Fast collaborative editor • @zencoderai - AI coding agent platform • @codeium - Free AI autocomplete • @tabnine - AI code completion • @supabase - Backend/database • @ChatGPTapp - General AI assistant • @AskAider Terminal-based AI pair programmer • @boltdotnew - Prompt-to-app generator
- 38Replies
- 14Reposts
- 112Likes
- 3.6KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post.
- 11
@patrick_oshag ·
Some early thoughts after building real apps by myself for the first time… We built an internal tool called Conveyor It’s an app builder, and internal App Store It is connected to all of our data, context, and external data APIs I’m completely and utterly useless as an engineer, but I’m good at knowing what I want a tool to do. I’d previously struggled to make useful programs with pure CLIs. Our wrapper made it easy for me. In the first 3 days of having this tool, I’ve built several fairly complicated applications, two of which I’ve used a ton for real work. I’ve only used a couple hundred million tokens so far. Some early feelings: 1) It’s obvious to my that my companies Positive Sum and Colossus will have fully bespoke operating systems, built in house. They will manage as much of our work as possible. This is already exploding for things like research and reporting. Every business will want this for themselves. Sure we won’t built our own slack, but we will built everything that pertains specifically to our shape as a firm, which is a lot. 2) x402 protocol (which enables AI agents and users to pay for API access and digital services instantly, without accounts or subscriptions) is immediately interesting to me. Many times I’ve wished I could just stream payments for individual data points. 3) right now each loop of prompt to output takes 5 to 15 minutes. As models and ASICs (@Etched !) make this faster, it’s going to be so much more fun. Even 5 minutes makes it hard to get in the flow. Can’t wait for seconds instead of minutes. 4) it’s so much easier to design things by starting with a shitty first draft of an app and seeing what’s wrong and iterating than nailing a full design ahead of time. When I had directed the design of software before this was always maddening and slow. 5) this has made me realize that my imagination had atrophied. Use it or lose it is real. Very quickly I’m finding it easier to have good ideas by building more stuff. I encourage everyone to do the same. So fun and rewarding. 6) We need more compute
- 21Replies
- 13Reposts
- 258Likes
- 30.5KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 12
@smratitiwa86867 ·
🚨 Most people think you need to learn coding to build apps. That’s outdated. You just need to learn how to talk to AI properly. Here’s how to use Claude Code like a pro (even if you’ve never coded before): First, set it up right: • Open Claude desktop app • Switch to Code mode (not Chat) • Connect your GitHub • Select your project folder Now the important part 👇 ⚡ Before you type anything, change these: • Model → Opus 4.6 • Turn ON → Auto-accept edits This removes friction. Claude works non-stop for you. Now stop writing technical prompts ❌ Most people do this: “Create HTML, CSS, use flexbox…” That’s WRONG. Instead, write like this ✅ “I want a clean landing page for my fitness brand. Big headline, 3 plans, testimonials, and a signup button. Goal: get 100 leads/week.” 💡 Pro move: Attach a screenshot of any website you like. Then say: “Build something like this, but for my brand.” Claude will: → Understand layout → Write code → Build UI → Connect everything 🚀 Want next-level results? Use this master prompt: “Create a GitHub repo named [NAME]. I don’t know how to code. Build everything for me. I want to [GOAL] for [SUCCESS CRITERIA]. Use this as reference [screenshot].” The shift is simple: ❌ Learn coding ✅ Learn prompting The people winning in 2026 aren’t developers… They’re AI directors. Follow Smrati Tiwari for more 🔖
- 22Replies
- 30Reposts
- 97Likes
- 2.6KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 13
@mark_k ·
News: @OpenAI just released Sites for Codex. At first glance it looks like a website builder. But it’s not really about websites. It’s about making small, useful apps on demand. Dashboards. Review tools. Project pages. Little internal workflows nobody wants to build properly. This is where Codex gets interesting: not just writing code, but turning random work into software.
- 31Replies
- 15Reposts
- 255Likes
- 18KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 14
@itsolelehmann ·
what's happening inside Anthropic right now is genuinely fascinating: DESIGNERS are now shipping production code with no engineer in the loop at all these are non-technical people with zero coding background. engineers on the team said designers are making "large state management changes you typically wouldn't see a designer making" think about what that means for a second. at every tech company in the world, designers and engineers are two separate roles. designers make mockups, engineers write code. that's been the deal for decades. at anthropic, that line is completely disappearing now. here's what their designers actually do now: it starts with a screenshot. 1) a designer takes their figma mockup and pastes the image directly into claude code. 2) claude looks at the image and generates a fully functional prototype from it. working code that engineers can immediately build on. this alone replaced the entire traditional cycle of: make static design → write spec → hand to engineer → wait → review → give feedback → wait again → repeat. but that's just prototyping. from there, designers implement front-end changes themselves. typefaces, colors, spacing, layout, etc directly in the codebase. no ticket filed, no engineer pulled in. and it goes further than visual polish. designers are now making state management changes (the code that controls how data moves through the app, even junior engineers find this tricky) and for their ongoing backlog of polish and bug fixes, they don't even open claude code. they just file a github issue (basically task description) describing what they want changed… and claude automatically proposes a code solution. then the designer reviews it and ships it. so there's a persistent stream of improvements flowing into production without pulling a single engineer off their work. they also use claude code to map out edge cases during the design phase. the stuff that used to only get discovered later when engineers actually built the thing. so now the designs are better AND they ship faster because the edge cases are already handled before engineering starts. one detail i love: they set up a custom memory file that tells claude: "you're working with a designer who has little coding experience. give detailed explanations. make smaller, incremental changes." claude adapted its entire approach based on that one file. here are some cool numbers, straight from the product design team: • claude code is now open alongside figma 80% of the time • 2-3x faster execution across the board. the designers' reaction when it all clicked: "holy crap, I'm a developer workflow" the boundaries between roles are dissolving. quietly. i think what's happening internally at anthropic is 2-3 years ahead of what will happen to the rest of the world
- 35Replies
- 16Reposts
- 146Likes
- 22.9KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 15
@shushant_l ·
I'm amazed most people still think you need to code everything manually. Here's how to build complete apps faster with vibe coding and AI. --- 1. Vibe coding lets you describe your app in plain English instead of writing every line of code. --- 2. Your AI assistant generates functional code, while you guide, refine, and debug the project. --- 3. The workflow follows a simple loop: Describe, Generate, Review, Iterate, and Deploy. --- 4. Start with a detailed prompt that clearly explains your app and desired features. --- 5. Let AI generate the frontend, backend, UI, and database structure automatically. --- 6. Review every output instead of assuming AI-generated code is production-ready. --- 7. Keep improving your prompts instead of rewriting everything from scratch. --- 8. Deploy only after testing your application thoroughly in a real environment. --- 9. Lovable is ideal for building polished full stack apps with minimal effort. --- 10. https://t.co/H9g78AyOFv is great for quickly prototyping ideas directly in the browser. --- 11. Cursor is one of the best AI-powered code editors for developers. --- 12. Claude Code provides a powerful terminal-based AI coding workflow. --- 13. Replit helps you build and deploy complete applications from your browser. --- 14. GitHub Copilot speeds up coding by assisting with suggestions, debugging, and code completion. --- 15. Give AI technical context before asking it to generate code. --- 16. Clearly describe features from the user's perspective to get better results. --- 17. Explain how new features should integrate with your existing application. --- 18. Ask AI to create implementation plans, write tests, and review edge cases. --- 19. Always check AI-generated code for security issues before shipping it. --- 20. Remember that your role is becoming the architect, while AI handles much of the implementation. --- To learn more, check the infographic. ---
- 8Replies
- 11Reposts
- 33Likes
- 2.1KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 16
@sentient_agency ·
10 FREE TOOLS THAT LET YOU BUILD YOUR OWN AI AGENTS WITHOUT WRITING A SINGLE LINE OF CODE Bookmark every single one. In 2026, you no longer need to be a developer to build an AI that works for you. You drag, you drop, you connect. Here's where to start. 1. https://t.co/MgNHdcMCR6 The one everyone's using right now. Drag visual blocks onto a canvas to build an agent that reads your email, researches a lead, updates your CRM, and pings you on Slack, all on its own. The AI Agent node connects to any model. Free forever when you self-host, and it's a top-50 project on all of GitHub for a reason. 2. https://t.co/UULgbO9ggl Build AI agents and chatbots by connecting nodes on a visual board, no code at all. Point it at your own documents and it answers questions from them. Free and open-source to self-host. The fastest way to turn a pile of PDFs into an assistant that actually knows your stuff. 3. https://t.co/S3A65MCUGa A full open-source platform for building AI apps and agents through a visual interface. Workflows, knowledge bases, and multi-step agents, all drag-and-drop. Free to self-host with a generous free cloud tier to start. One of the most complete no-code AI builders that exists in 2026. 4. https://t.co/vn4BLaA27N Lay out your agent's logic visually, like a flowchart, and watch it run. Built on the same ideas powering serious AI apps, but with zero code required. Free and open-source. The tool that makes "how does an AI agent actually think" finally click, because you can see every step. 5. https://t.co/GWNC2Yag9i and https://t.co/6futH5rZIE Open-source, no-code automation built for the AI era. Connect your apps and drop an AI step into any workflow to make it smart. Free to self-host. The open answer to the expensive automation tools, with AI baked in from the start. 6. https://t.co/3KGkT77G0o A visual automation canvas with a free tier and built-in AI modules. Connect thousands of apps and let an AI agent decide what happens next. More beginner-friendly than the code-leaning tools, and you can build a working agent in an afternoon without touching a terminal. 7. https://t.co/rQJzWLcBA4 Build conversational AI agents that talk to customers, qualify leads, and answer support questions, all through a visual editor with a free tier. The no-code way to put an actual working agent on your website or WhatsApp this week. 8. https://t.co/V7rHHsyoJt Design AI agents that hold real conversations, by mapping out the flow visually. Popular with teams building customer-facing assistants. Free tier to start. You draw the conversation like a map, and the agent follows it. 9. https://t.co/Ids0WSOgzQ (Gemini in Workspace Studio) Google now lets you build automated AI workflows right inside Gmail, Sheets, Drive, and Chat using plain-language instructions. Describe what you want in a sentence and Gemini wires it up. The agent builder hiding inside tools you already pay nothing extra for. 10. n8n-io/self-hosted-ai-starter-kit on GitHub The shortcut. n8n's official starter kit spins up a complete local AI setup, the builder, a local model through Ollama, and a vector store, with one command. Everything runs on your own machine, fully private, completely free. The fastest path from zero to your first working agent. One honest note for 2026: the builders are free, but the AI thinking still costs pennies per run if you use a paid model like GPT or Claude. Run a local model through Ollama and even that drops to zero. Most people are still just chatting with AI. The ones paying attention are building little workers that run on their own. The barrier used to be code. In 2026, it's gone.
- 4Replies
- 11Reposts
- 38Likes
- 2.7KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 17
@toddsaunders ·
The funniest pattern with blue collar builders. Stage 1: "AI is for tech people, not for me." Stage 2: A friend shows them something they built. They're curious but won't admit it. Stage 3: They try Claude Code for one small thing. A unit converter or a simple form. Something they'd be embarrassed to tell anyone about. Stage 4: It works.... They stare at their screen like they just pulled a rabbit out of a hat. Stage 5: They disappear for two weeks, staring at their computer screen more than ever. Stage 6: They resurface with three monitors, a custom domain, and a full product demo for software that doesn't exist anywhere else on earth, because they understand the long tail nuance of the problem. I've watched this happen with plumbers, foresters, roofers, HVAC techs. The trade doesn't matter, and the arc is identical. The gap between "I can't build software" and "I just built software" isn't skill anymore.... It's one working demo. One moment where the thing you described in plain English actually appears on your screen and works. After that, there's no going back. It's funny because Silicon Valley spends millions on developer evangelism. But it turns out the best evangelism strategy is a contractor showing another contractor what he built over the weekend. Let the builders build!
- 19Replies
- 5Reposts
- 85Likes
- 6.5KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 18
@lemire ·
Will a new engineer know how to read code? When I was a kid, most people did not know how to type. We had an actual typing class where you had to learn the technique. The final exam was a speed typing test: how many words a minute could you type? You are not going to impress anyone today by saying that you can type on a keyboard. In fact, only 40 years ago, the default was cursive writing. Yet cursive writing is going away. Increasingly, kids cannot read or write in cursive. We type all the time. We forget how many of our skills are learned—and how many are forgotten. Reading and writing in English or Persian is not innate. Writing integrals is not innate. Reading and writing code is not innate. They all require substantial training. I have now encountered more than one student who could use AI to build an application but who cannot read or write code. It is not entirely new. We have had “non-technical” people in software forever—people who tell you how they built this or that, or how they designed the first X or Y. In fact, the standard a few decades ago was that once you had a university degree, you were not supposed to code. You were an analyst. Coding was for monkeys or low-status employees in many organizations. I am an actual university professor and I code. I code boring stuff in Java, C, and Python. Few professors code. It is low status. So why do I do it? What about top engineers? The engineer paid a million dollars a year at Google or Meta knows how to write code. They can often read and write in assembly and TypeScript. They know it all. In effect, whether you should learn to write code has always depended on context. If you work for a typical government agency, code is entirely secondary. It is as important as how the chairs are nailed together or how the windows open. It has to work, but nobody cares beyond the strict minimum. But you are not going to earn $1M a year writing code in a government agency. So what will happen? My theory is that what will happen is much like what happened with the arrival of television and video. It was felt that people would stop reading. We would go back to the world of Socrates, who famously resisted the written word. But the opposite happened. We have never read and written as much as we do now. And there are more people than ever making a living while writing all day long. I suspect that top engineers will end up reading code, and sometimes writing code, at speeds previously limited to a tiny elite. These top engineers will not be everywhere. They will not be in every organization. But they will pack a punch. Why? Because we do not have a better alternative for communicating software from brain to machine and machine to brain. “But Daniel, people say that software programming is a solved problem. Why would anyone read or write code in the future?” You have to be careful with your models. When television arrived, people predicted that we could just replace the university lecturer with a TV show. In some respects, this model is not wrong. But it did not happen because the job of the university lecturer was never to offer the equivalent of a TV show. Similarly, the Google engineer paid $1M a year was never a machine to produce code. Nobody actually wants code, just as nobody wants text. Here is what concretely is going to happen to an engineering team where nobody can read or write code. They will be reading what the AI says about the code. And they will understand about as much as a manager understands the code written by their engineers: not much at all. The reason we pay an engineer $1M a year is because he understands concepts that few people do. He can outrun others because he understands the problems more deeply. And reading and writing code, a lot of it, is part of how you get deep insights. Chatting with Claude Code won’t turn you into a top 1% programmer.
- 7Replies
- 8Reposts
- 75Likes
- 7.2KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 19
@1Umairshaikh ·
The real no-code founder arc: → see someone make $4k/month with a simple tool → spend 2 weeks finding the "perfect" idea → spend 3 months perfecting the UI → write a launch post nobody reads → blame the market the market was fine you never actually talked to anyone
- 31Replies
- 3Reposts
- 33Likes
- 723Views
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 20
@Layton_Gott ·
In 2-3 years nobody is going to care if you can write code from scratch. They're going to care if you can build products. Every month AI gets better at writing code. Every month the gap between "vibe coder" and "traditional coder" gets smaller. Every month the thing that actually matters shifts further from syntax to vision. The devs clowning on vibe coders right now sound exactly like the people who said "real programmers don't use IDEs" in 2005. I build Scribe almost entirely with Claude Code. I describe what I want. It builds it. I review it, test it, and ship it. The product works. Users don't care how it was made. The skill that lasts isn't writing code. It's knowing what to build, how to architect it, and how to get it in front of people. Learn to code if you want to. But don't let anyone tell you it's a requirement to build software anymore. It's not.
- 40Replies
- 5Reposts
- 45Likes
- 2.1KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 21
@shushant_l ·
I'm shocked people still think building an app requires 6 developers, 47 meetings, and sacrificing your weekends. Here's how to build apps with AI while your coding experience is basically "I once changed my Wi-Fi password." --- 1. Start with the problem, because "I want an app" is not a product strategy, it's a shower thought. --- 2. Write a clear spec explaining who it's for, what it does, and why anyone should care. --- 3. Give AI context because "make me a social media app" is how you accidentally invent Facebook's unemployed cousin. --- 4. Pick an AI app builder based on what you're making, not whichever one has the coolest landing page. --- 5. Use Lovable or Base44 when you want to go from idea to working web app without marrying a code editor. --- 6. Try Bolt when you want rapid prototyping and enjoy watching prompts turn into software suspiciously fast. --- 7. Use Bubble when your app needs serious workflows and you've accepted that "no-code" can still have homework. --- 8. Choose Adalo or FlutterFlow when your brilliant idea absolutely needs to live inside someone's phone. --- 9. Use Cursor, Replit, or Windsurf when you're comfortable with code but would prefer AI do some of the suffering. --- 10. Generate the first version quickly because version one is supposed to exist, not win a design award. --- 11. Test every screen because AI is incredibly confident, including when it has created a button that does absolutely nothing. --- 12. Check every workflow because "it looked fine in the preview" has destroyed many peaceful afternoons. --- 13. Fix one problem at a time instead of sending AI a 900-word emotional breakdown of everything that's wrong. --- 14. Iterate with specific instructions like "make this button larger," not "bro please make the app better." --- 15. Never trust generated code blindly because AI can write bugs at approximately the speed you can say "wow." --- 16. Check authentication, payments, permissions, and security before inviting the entire internet inside. --- 17. Make sure you can export your code before committing, unless vendor lock-in is part of your retirement plan. --- 18. Deploy once the core experience works because polishing forever is just procrastination wearing a product-manager badge. --- 19. Remember that AI handles more of the coding now, but you still need the idea, logic, taste, judgment, and functioning brain. --- 20. Your competitive advantage isn't typing code faster anymore, it's knowing exactly what should be built and why. --- To learn more, check the infographic. --- Get all my visual guides for free here: https://t.co/p3DBZe1GLQ ---
- 8Replies
- 6Reposts
- 34Likes
- 1.8KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 22
@Jacobsklug ·
I run a one-person content business with Claude Code. The machine writes, I approve. Haven't touched the keyboard in 3 weeks. Here's how the whole thing runs: 1/ Routines Jobs that fire on a trigger. Draft the posts, pull the ideas, build the outline. Most run in the cloud on a schedule, so they work even when my laptop is shut. 2/ Scheduled tasks For the jobs that have to touch my actual machine. LinkedIn has no clean API, so a task opens Chrome and reads it the way a person would. No API, use the browser. 3/ Skills A capability you build once and reuse everywhere. My voice is a skill. My review process is a skill. Sharpen it one time and every routine that loads it gets better. 4/ Connectors The bridges out to your tools. @NotionHQ, @typefully, @SlackHQ, my scraper. Cut the connectors and the system just talks to itself. 5/ Databases The memory. @NotionHQ holds my trends, my ideas, my analytics, my approval queue. Every routine reads from it and writes back to it. 6/ Dashboard Using the @Lovable MCP I describe a dashboard to Claude in plain English and it ships the interface and the database behind it. None of this is complicated. Connectors reach your tools. Databases hold the memory. Skills are the reusable brains. Routines run the jobs. Stop making content. Build the machine that makes it.
- 6Replies
- 2Reposts
- 21Likes
- 2.2KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 23
@Hartdrawss ·
How to build a cash-flowing product with Claude Code : find a painful workflow in a boring industry → don't build for tech people → build for the accountant who still uses excel for everything → the restaurant owner tracking inventory in a notebook → the pain is obvious. the solution doesn't exist yet. talk to 10 people who do that workflow → don't assume. ask. record every tool they use, every spreadsheet, every manual step they hate doing → the gaps between tools is where your product lives. open claude code before you open figma → describe the full product in a single markdown file → what it does, who its for, what the core workflow is → drop it in as context. this is your spec. claude code works best when it knows the whole picture upfront. let claude code scaffold the entire project → next.js, supabase, tailwind, stripe → don't touch the boilerplate yourself → your job is workflow logic, not setup → tell it the stack, tell it the schema, let it build the skeleton while you think about the product. build the hardest feature first → not the landing page. not the auth. the core thing that makes the product worth paying for → if you cant get that right nothing else matters. when claude code hallucinates → don't restart → reduce scope → break the feature into smaller pieces → give it one job at a time → the quality of your prompts is the quality of your product. use claude code to write your own cursor rules → let it document every decision it makes → stack, conventions, component patterns → drop those rules into your next session → the agent remembers nothing. you have to make it remember. ship to 3 customers before you build anything else → watch what they actually use → the thing you built for isn't always the thing they need most → one of your features will surprise you. pay attention to which one. charge per outcome → per report generated, per hour saved, per workflow automated → the ROI conversation takes 10 seconds when its tied to a real result → never charge per seat. build content around what you learned → not "building in public" content → the specific claude code trick that saved you 4 hours → the prompt pattern that finally got the schema right → the stuff only someone who actually built this would know → become the person for that niche. your competitor can clone your product → they can't clone 3 months of customer feedback and iteration baked into the codebase → that accumulated context is your moat → keep shipping.
- 7Replies
- 4Reposts
- 24Likes
- 879Views
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 24
@joncphillips ·
My co-founder started using Claude Code a few weeks ago. He’s not a developer, never has been, and now he wants to (and can) build things. I’ve been watching this exact shift play out with other people in my life over the last year and every time it happens I’m struck by how quiet the transition is. One week they can’t build, the next week they can. It’s fucking incredible.
- 32Replies
- 2Reposts
- 45Likes
- 1.4KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 25
@Rakshaweb3 ·
3 days ago I had an idea and zero front-end skills. Today I shipped this 👇 https://t.co/lBcDfzNpmq Not because I learned to code overnight but because I learned to direct AI like a design partner. Every section, every word, every pixel reviewed, rejected, rebuilt until it felt right. AI didn't build this website. I did. AI just held the tools. If you're a founder sitting on an idea because you "don't know how to code" that excuse expired this year.
- 7Replies
- 3Reposts
- 41Likes
- 602Views
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 26
@sourfraser ·
I have zero coding experience, yet I've built 3 internal tools that help run our agency. No developer or budget needed. Just a few spare hours. These are the 3 internal tools we use every day at Fraggell: 1) HR App We were paying £40/month for some bloated HR platform. Using maybe 10% of the features. So I built my own. • Staff log in • Request holidays • Report sick or WFH. It tracks everyone's holiday balance. Syncs to a team calendar that feeds straight into Google Calendar. Also groups people by department. So when someone requests time off, we never approve it if someone else in the same team is already out. First vibe code thing I ever built and it only took an afternoon. 2) Fraggell AI Studio The team was jumping between like four different AI video platforms depending on the client. So I built one platform that wraps all of them: • Sora, VO 3.1, Kling. • Every resolution • Every aspect ratio. • Character consistency for Sora built in. • Upscaling. And a filter system so they can label everything by brand when they're working across multiple clients at once. It’s also ludicrously cheaper than paying for all the subscriptions separately. 3) UGC Shipment Tracker UGC shipments are the bane of our lives. We were manually copying tracking numbers for every single creator. It was a nightmare. My business partner built this. One dashboard with every shipment going out to creators across the entire company. Auto-tracks delivery. If a creator gets their product and doesn't send footage within 5 days, it automatically pings the relevant team member. If they still don't respond, it escalates. We call them. None of this required a developer. Just a bit of time and a clear brief on what you actually need. If you're running an agency and you've got manual processes eating your team's time, build the tool. It probably takes a day.
- 3Replies
- 4Reposts
- 28Likes
- 2KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 27
@heystevetan ·
A broccoli farmer in Hokkaido, Japan built his own farm management system using Codex. No farming experience. No engineering degree. Started as a civil servant. He couldn't afford an engineering team and built these tools himself: → Remote greenhouse vent control using a chatbot → A bot that monitors temperature and opens vents automatically → Satellite crop-health data mapped over his own fields → A full operations base linking plots, tasks, materials, and sensors → Wiring diagrams of his electrical panels, generated from a photo An engineering firm would charge $500,000 + six months to build this. He did it with a laptop and an AI coding tool. 2 years ago, this wouldn't just cost you money. It would cost you an endless cycle of delays, weeks of meetings, and back and forth between teams. And the end result would still look nothing remotely close to your initial idea. This guy had an idea for the tool he wanted. Built it. Deployed it. And is using it. All by himself. Without it costing him his peace, time or money. AI has collapsed the barrier between idea and execution. There's never been a better time to build and those doing it now will win the next decade. If you're an old-school operator with your "AI has nothing to do with my business", think again. Your biggest competitor is a guy who knows his shit with a laptop and codex.
- 0Replies
- 2Reposts
- 38Likes
- 2KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 28
@nikil ·
After 2 years of trying, I finally last week got everyone in my family to vibecode an app / set up an openclaw Sharing learnings to hopefully help you convince your family of the joy of building 1. pick something THEY like - my dad build a stock advisor to show him insights & what to buy - my mom built a supplement tracker (had tried multiple & didn't find what she wanted) - gf built an AI news tracker I tried literally for years to get them to build stuff I thought was cool. Automating text messages, personal website, life assistant, etc... They weren't interested. As soon as I said "What would be really cool that you really want?", they thought for a bit, came up with the idea, and then immediately wanted to do it. learnings: - this was really obvious, I should have done from the beginning 🤦♂️ - most people who aren't engineers don't even realize the possibilities of what they can build - brainstorm with them to show them they can build ANYTHING 2. SHOW them apps non-technical people built the most common hesitation I heard was "I'm not an engineer, you've been coding for 20 years" I tried telling them, "no anyone can build now". There was still this mindset of "you just think that because its so easy for you". Then I showed my parents the site my gf (who had never coded in her life!) made. Inspired them to try because they realized a non ultra-nerd could make a full site so easily. 3. make it FUN @TaraViswanathan, @_jordanstern and I put our OpenClaws in a imessage groupchat. The AI (Dave, Kevin, Eva) are absolutely ridiculous - you walk away for 1 minute and there are 187 messages of them roasting each other, dating, and naming their kids (Pepperoni) 😂 At dinner, Tara and I would be cracking up and show my mom snippets from the group chat. The next week she set up her openclaw. Before it was a chore "i should learn AI so I don't get behind in life". Now it's exciting "this is so fun!" 4. HAND HOLD them through it This stuff is easy for you. your body runs off of protein, X and your claude code max subscription. this is still hard & confusing for most people. before I had said "just watch a youtube video and try it - its easy" then I sat down with my dad and walked him through. big realization for me: there's a lot of stuff you have to learn that we take for granted just to get a basic site up - where is the claude code install on the website? - how to install a DMG? - can't find code tab in claude? - oh bc it requires paid account. how to upgrade? - error because no brew or npm installed? - hit pro limit, upgraded account, still limited? - fire up terminal to work around - what is "git" - how do I go to the site? - how do I view it on my phone? and 276343 more questions we sat down for 3 hours and got it done! but unless you had built stuff before any of these frictions would have stopped him. its not just for my dad who was a doctor. the same day, a sharp founder / vc buddy had messaged me saying "Dude I’m dying setting up Claude. Feel like it could be an episode of Silicon Valley. In a death loop where somehow I managed to confused the smartest thing on the planet haha" (and this isn't just claude - even down to getting set up on a mac requires new skills) Coding is as easy as breathing for you. Turns out we're fish living in the water and most humans breathe air. 5. Get to magic moment FAST Build something simple & easy. That you can 1 shot and works on the first run. Can iterate from there. Once you see your site up, the excitement (& addiction starts). Dad didn't want to try coding for years. 9:30pm: "Need to sleep, waking up at 5am for flight" 11:00pm: (after 1.5hr setup) "i'm so sleepy, lets just do it tmr" 11:05pm: (hit run on site) "WOW!!!" 12:30am: "THIS IS AMAZING!" just like building a product -> faster you get to magic moment, faster they are hooked. -- Hope this helps you get your family excited about building! Once you pop, the fun don't stop!
- 10Replies
- 2Reposts
- 45Likes
- 5.2KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 29
@betomoedano ·
AI has changed the way software is built. As an experienced engineer, I can confidently say that it’s absolutely possible to build, deploy, and maintain an app without writing a single line of code. Writing code by hand is no longer necessary. But that doesn’t mean anyone can simply prompt an AI to build an app and succeed. This is why experienced engineers are seeing incredible productivity gains. They already have the knowledge and mental models needed to guide AI in building real software. Non-technical people who want to build an app without learning to code don’t need to learn coding syntax. They need to understand how mobile apps are built, maintained, and deployed.
- 7Replies
- 3Reposts
- 57Likes
- 3.6KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 30
@gaetano_nyc ·
A lot of my clients are telling me that deals are stalling in the pipeline because of "buy vs build" dilemma. With coding assistants and low-code development apps, companies are going for more open source solutions and building on their own instead of buying SaaS... especially for basic things like a simple iPaaS, data integrations, reporting and dashboarding tools, etc. One customer even built their own solution and canceled his SaaS subscription. This is not being talked about enough.
- 12Replies
- 1Reposts
- 22Likes
- 1.2KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 31
@PrajwalTomar_ ·
I still don't think people understand what just shipped. I gave my coding agent one prompt and DeepSpace built me a full multiplayer kanban. → Sign-in with Google or GitHub → Live cursors on the board (like Google Docs) → Cards syncing across browsers in real-time → One command to deploy Most builders are still gluing 5 different services together to ship something half this complex. This is the stack I have been waiting for.
Watch video- 3Replies
- 7Reposts
- 20Likes
- 2.1KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 32
@JustAnotherPM ·
Here's what 40 PMs with zero coding experience shipped in 8 weeks: • Room redesign AI from photos • Sari recommendation engine • AI resume coach • Invoice reader • Brand-aware social media generator • Makeup review browser extension • Exam prep app for 8th graders • Mechanic price validator All live. All working. All at real URLs.
- 3Replies
- 2Reposts
- 10Likes
- 1.4KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 33
@toddsaunders ·
"Blue collar workers can't build software." This is favorite commentary every time I post about blue collar builders. It's funny..... because they said the same thing about Shopify merchants. Nobody looked at someone setting up a Shopify store and said "wow, look at this non-technical person learning to code." They said "that person is building a business." The software was incidental, but the outcome was the point. Same thing is happening right now in the trades. A plumber using Claude Code isn't "learning to code." He's building a quoting tool that works the way his business actually works. Because the one he's paying $1,200 a month for doesn't. The framing is completely wrong. These aren't non-technical people becoming technical. These are domain experts who finally have tools that speak their language, and solve their deepest most nuanced problems that only they understand. The right question to be asking at this point is "what happens when the people closest to the problem can finally build the solution?" IMO what happens is better software that actually has domain expertise well beyond a workflow and inference. Nobody calls a Shopify merchant a "software developer." Stop calling a tradesperson with Claude Code one as well. They're builders. That's what they've always been.
- 8Replies
- 1Reposts
- 27Likes
- 2KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 34
@jspeiser ·
The funny thing about no-code tools like OpenClaw: they’ll get so advanced that non‑technical peeps like me can’t safely run them alone. Once you have: • Bots that remember things and act over days, they start “going off script” and you need someone who can debug their memory. • Multiple AI providers, rate limits, apis, and costs to juggle, you need someone who understands how the pipes actually work. • Automations that can send emails, change data, touch customers, you need guardrails, testing, and logs or they’ll quietly break things. • Giant drag‑and‑drop flows with 30+ steps, it’s no longer “no‑code”, it’s just messy code in boxes. In the end, you don’t replace developers. You just move the code from a text editor into a flowchart. Am I wrong?
- 21Replies
- 0Reposts
- 29Likes
- 5.2KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 35
@ericdjav ·
I use Claude to build my entire app. Here's my actual workflow: → I describe the feature in plain English → Claude writes the code → I review, test, iterate → Ship to 2,580 users I don't write code. I write product specs to an AI that writes code. My job title should be "AI Product Director" but I still call myself a founder. The skill ceiling moved from "can you code this?" to "can you describe what to build clearly enough?" That's the real AI shift nobody's talking about.
- 11Replies
- 0Reposts
- 14Likes
- 647Views
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 36
@kritarthmittal ·
the biggest advantage in business used to be capital. then it became distribution. now it's speed. a year ago, even building with AI felt like work. you still needed devs, designers, multiple tools, and plenty of trial and error. today my workflow is much simpler. build an app with superapp ai. generate ugc with arcads. automate the backend with n8n. ship. the crazy part isn't that these tools are perfect. they're not. they break, hallucinate, and overpromise all the time. the crazy part is that i barely think about hiring anymore. my first instinct isn't "who can do this?" it's "which tool should i use?" that shift happened much faster than i expected. last week i built an app and created ads for it in less time than it took me to edit the launch video. not mockups. not concepts. something real. which makes me think the bottleneck is moving. building is becoming easier. getting people to care is becoming harder. soon, almost everyone will be able to build products. the winners won't be the people with the best technical skills. they'll be the people with the best ideas, the best distribution, and the ability to test faster than everyone else. most importantly, we're still using the worst versions of these tools we'll ever see. next year's models will be faster. cheaper. more capable. what feels impressive today will eventually feel ordinary. i don't think we've fully processed how much that changes the way companies get built. what AI tools have become part of your daily workflow? always looking for underrated ones to try.
Watch video- 12Replies
- 9Reposts
- 27Likes
- 15.5KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 37
@chhddavid ·
$270k. that's what it used to cost to make a website look like real expert humans made it. thats over. I've been vibe coding websites and mobile apps for over a year and I honestly believe there's no difference between "indie hacker" and "VC-backed SaaS with 35 employees" anymore... but this is different. type out your thoughts and ai... adapts. design, code, monetization, launch, email marketing - you're not doing anything anymore, just approving/disapproving AI's decisions the skill now is SHIPPING. knowing what sticks and what doesn't, then doubling down on what actually works an old friend of mine has 0 technical ability. literally none. created his own calorie tracking app two weeks ago and it's better than half the agency work I've seen the last 6 months. took him <18 hours... and he didn't code/design/write a single thing. he just took an already-validated idea and made it his own... https://t.co/h8lDo5BTV6
- 8Replies
- 0Reposts
- 6Likes
- 499Views
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 38
@degensing ·
everyone's shipping faster. that's the problem. vibe coding, no-code, ai scaffolding. the floor dropped out. a working app in 48 hours is table stakes now. so why are most products still broken? because "working" means two different things: • working code runs without errors. • working products run without confusion. • working code passes the build. • working products survive the second session. one is a technical bar. the other is a human one. founders optimized for the first bar and called it shipping. then wondered why retention was flat and support queues were full. the real cost of shipping fast isn't technical debt. it's the gap between "it works" and "it works for someone." speed got you to launch. iteration is what gets you to product. what did your last v1 teach you that your plan didn't?
- 2Replies
- 4Reposts
- 11Likes
- 444Views
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 39
@mikemillercyber ·
Do you believe in Vibe Coding? If not, Here are 5 Reasons you should. Your career may depend on it. In fact, you can now get certified. At the middle of last year, I laughed at the term "Vibe Coding". I told myself it was a fad that would disappear. I was absolutely wrong. There's a plot twist at the end of this story, but first let's talk about facts: Here are some Facts: ✅ The software barrier has collapsed - You no longer need to memorize syntax to build applications that solve problems. Now you can do it with well thought out keystrokes. ✅ Senior engineers are embracing it faster than juniors - the people who understand it best are using vibe coding as a force multiplier, especially to do the tedious time consuming tasks ✅ Non-developers are now creating real software - ANY team, not just your development team, has the ability to produce software in real time. ✅ The time to MVP (Minimum Viable Product) has gone from months to days (and sometimes hours) ✅ Companies care about outcomes, not how the code was typed Now, before I go any further, I'm going to give a disclaimer. As someone who has been in Tech | Cybersecurity for 30+ years, security of these applications is key. Software should not be shipped unless it has gone through the full security process. With software development comes vulnerabilities. If you don't have a security mindset when developing your application, you need to team with someone that does. All of that said, get this: 👉 Vibe Coding Certifications are Emerging. Formal programs and certs are already popping up, which help organizations determine who can responsibly use AI to design, build, and ship software. The plot twist? As I mentioned at the beginning, last year I thought this was a fad that would go away. It didn't. In fact, I dove in. For years, I had been dreaming of an app that could work as a complete start to finish content creating platform for marketing departments, salespeople, businesses, or even people building a personal brand. During that time, it was just untouchable. Vibe Coding changed that. Last year I built it. What was previously priced as a 30k project, cost me $0. I leveraged AI and turned my dream into a reality. Am I a software developer? Absolutely not. Did I build a product that is being used by marketing teams, businesses, and content creators across the nation? Absolutely, but only because Vibe Coding exists. Tools I used: Cursor (IDE) - coding platform Claude Code - the brains Vercel - the host Supabase - the database Clerk - authentication Stripe - payments My dream to reality? It's called YORP (Your Online Reach Platform) 👉 https://t.co/xzNPSfMxdY
- 1Replies
- 1Reposts
- 10Likes
- 1.3KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 40
@EugenioFierro3 ·
Canva Code 2.0 turns prompts into published sites Canva just opened up its AI coding tool to its entire community, over 265 million monthly users, free accounts included. Describe a website, app or interactive experience in plain language, then edit it like any other Canva design. No code editor, no technical intimidation. 🚀 Starting this week, Canva Code 2.0 is available to the entire Canva community across every pricing tier, including free accounts. It's Canva's most aggressive move yet into the fast-growing vibe coding market, a category that barely existed 18 months ago but has already produced billion-dollar startups like Lovable and Replit. 🎯 Where rivals such as Lovable, Replit and https://t.co/NnxcsnQG1l focus on generating functional code from text, Canva is betting on a different problem. Danny Wu, Canva's Head of AI Products, put it bluntly: "We are deliberately targeting non-technical users. Canva Code isn't a tool we're building for developers." His argument is that most vibe-coded output looks generic, and in a world flooded with AI content, that sameness is what actually costs you attention. ⚡ The technical upgrades back that up. Canva says it has cut code generation time by 75% and the median time from prompt to published site by 30%. You can now start a Canva Code project right inside another design, as a page, in a whiteboard or a deck, import HTML from other AI tools, and pick from more than 50 new templates before dragging in assets from Canva's 120-million-item library. 🌍 When it's time to ship, you can buy a custom domain inside Canva, publish to a free domain, or lock things down for a team with single sign-on. Since Canva Code first launched a year ago, the community has already built more than six million sites, from classroom hubs to real estate listings. Why it matters: for creators, small businesses and educators, this lowers the barrier to shipping a working landing page, quiz or calculator without hiring a developer. But it's worth being precise about the boundaries here too: Wu himself admitted Canva Code is "probably not going to be suitable" for sites with complex backends or hundreds of thousands of daily visitors, and there's currently no e-commerce support built in. What strikes me most isn't the speed numbers, it's the honesty. Admitting what a product can't do is rare in AI marketing, and it actually makes it easier to decide whether Canva Code is the right tool for a quick prototype versus a real Lovable or Replit build. Whether "making the output look good" is enough to hold its own against dedicated vibe-coding platforms racing toward serious revenue is the real test still ahead. 📱 Want AI updates on WhatsApp? DM me "AI" and I'll send you access. 🔔 Follow me for the last AI updates! #AInews #CanvaCode #VibeCoding #AITools #NoCode
Watch video- 3Replies
- 2Reposts
- 5Likes
- 306Views
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 41
@anulagarwal ·
i uninstalled all IDEs/code editors from my system earlier this year. not because i became a better developer. because the models and agentic coding tools became too good i don’t really read the code anymore -> i just prompt, wait, test, complain, iterate. this works for almost any digital product you want to build: apps, games, websites, tools. in most cases, i create a base template with 75% of the features already built, so i don’t have to prompt and test the same things again and again. the funny part is, i used to think coding was the hard part. now the hard part is explaining exactly what i want without sounding like a client from hell. sometimes, you are not the developer anymore. you are just the QA intern for a very confident robot.
- 2Replies
- 0Reposts
- 12Likes
- 987Views
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 42
@_vmlops ·
A NON-DEVELOPER JUST SHIPPED 70K LINES IN 30 DAYS Here's what he learned: ▫️ start with a PRD...AI executes your mess faster, it doesn't fix it ▫️ new session per new thing...plan smart, build cheap ▫️ UI first, backend second ▫️ tests from day one... regressions will wreck you ▫️ git from line one..he started at 16k & regretted it ▫️ two models > one... the original author always misses things ▫️ security basics before you build, not after you don't need to be a developer to ship real things you need to be organised, patient & paranoid in the right places https://t.co/AUYbwAtXgD
- 0Replies
- 0Reposts
- 7Likes
- 562Views
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 43
@Joey_Walker82 ·
Still building without code and loving it to be honest. I was sceptical at first, but was quickly blown away. Here's my go-to stack for cranking out SaaS products fast: • @Lovable for web apps • @rork for mobile • @supabase as my database Been using these to build @CTRLoop and Problem Scout. Not perfect but gets products shipped whilst the "real devs" are still planning. 10 minutes here, 20 minutes there. It all compounds.
- 2Replies
- 0Reposts
- 4Likes
- 74Views
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 44
@TaylorPearsonMe ·
I recently went back and re-watched Bret Victor's 2012 talk "Inventing on Principle" on YouTube. His core principle has stuck with me: creators need an immediate connection to what they're making. You change something and see the result right away, instead of writing code, compiling, waiting, and picturing it in your head. To make the point he built these incredible demos where he would edit a line of code and the game updates live. Drag a number and the drawing redraws in real time. I've been thinking about that talk while building a landing page today. I'm building it in Astro through Codex. I just say what I want in plain language: center this heading, add some padding, put an image here, etc. It happens in a few seconds, and I look at the page and say the next thing. It's exactly what he meant and it's absolutely addictive. The loop is tight enough that I lose an hour without noticing. That connection used to run through code, but now it runs through plain language, which means it belongs to anyone who can say what they want. It's not a clean match for his vision. Describing intent to a model is fuzzier, and sometimes I get the wrong thing, but the loop is fast enough that you iterate toward what you want instead of specifying it up front. (There's some Coase angle in here about how like you just make more and new stuff because there's no handoffs too)
- 1Replies
- 0Reposts
- 7Likes
- 1.1KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 45
@rfradin ·
"In 2026, every employee will be a developer." That’s the marketing pitch for the no-code revolution. To me, it sounds like an operational risk. If you have 5,000 employees and they all start building their own autonomous agents to solve their own problems, you don't get digital transformation. You get a digital junk drawer. Here is what that looks like in practice: - Ten different employees building ten slightly different agents to process the same invoice. - Zero documentation on how any of them work. - No ability to take a win from one department and scale it to the enterprise. The problem isn't the intent; employees are trying to be productive. The problem is the redundancy. Without visibility, everyone builds from scratch because they don't know a solution already exists, or is under construction. We are moving from a phase of creation to a phase of curation.
- 0Replies
- 0Reposts
- 4Likes
- 196Views
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 46
@TheJobfather__ ·
No-code tools are a real entry point. Learn how to connect forms, databases, email, Slack, CRMs, spreadsheets, and AI steps. Companies still need people who can make tools talk.
- 0Replies
- 0Reposts
- 5Likes
- 451Views
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 47
@JulianGoldieSEO ·
Google AI Studio just killed the “I need a developer” excuse. You can now: → Type an app idea → Build it with AI → Connect Gmail, Docs, Sheets, and Drive → Test it on your phone → Deploy it live with one click No coding. No servers. No tech headache. One person can now go from idea to live app in one sitting. The new skill is not coding anymore. It’s knowing what to build.
Watch video- 1Replies
- 0Reposts
- 2Likes
- 228Views
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 48
@edmundtian ·
I haven't coded in over 3 years. Last week I downloaded Claude Code and holy shit this is literally 20x easier than it was in 2022. You tell Claude Code what you want to build and it will 1. design the system architecture 2. write the code 3. run it to make sure it works 4. if not, repeat from step 1 until it does Ppl used to call it your own personal junior dev. But now it's more like your personal army of TECH LEADS. The technical barrier to building software is now zero. Everyone should be tinkering with this today. Especially ppl like creators who have the marketing side down. 🎒 Here's your vibe-coding starter pack: Vercel = one-click deploy. Supabase = auth + database in minutes. Stripe = handle payments and subscriptions. Claude Code = writes code, runs it, debugs it, fixes it.
- 0Replies
- 0Reposts
- 3Likes
- 267Views
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 49
@_vmlops ·
OPENAI JUST SHIPPED SITES IN CODEX turn any idea into a deployed app in minutes, from a conversation → no infra setup → no deployment code → auth, storage + db out of the box → share with your team via chatgpt login the use cases they showed: → account lens (pre-meeting intel for execs) → event summit prep hub → compass memo (investment proposals) and you can keep refining through chat no context switching, no engineers needed from trusted context to a working app your whole team can open this is what "agentic workspace" actually looks like in production
Watch video- 4Replies
- 1Reposts
- 0Likes
- 477Views
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post. - 50
@TheJobfather__ ·
Non-programmers can now build things they could never ship before. The next step is learning enough about tests, security, databases, users, and deployment to avoid building on quicksand.
- 0Replies
- 0Reposts
- 3Likes
- 1.3KViews
Rewrite this post in your own voice and angle.See the hook, structure, and reusable template behind this post.
Best No-Code tweets
Write posts like these, in your own voice
Xholic studies what works in your niche, drafts posts in your voice and schedules them for the hours your audience is online.
Start 7-day free trialTry the live demoTake a 2-minute tour of a sample account in the real app. No sign-up or login needed.
No card needed · Nothing to cancel
Browse all tweet collectionsLive demo: no sign-up or login needed · takes about 2 minutes
Keep exploring
From the blog
- Twitter API Examples: A Practical Guide for BuildersExplore real Twitter API examples with code, auth flows, rate limits, and patterns for posting, streaming, analytics, and growth workflows on X.
- 10 X Analytics API Alternative Options for 2026Compare 10 X analytics API alternatives for 2026, from low-cost data providers and custom scrapers to enterprise listening platforms.
- Twitter Automation Strategy: A Safe Playbook for 2026Build a safer Twitter automation strategy with clear goals, human review, policy guardrails, practical tools, and a weekly measurement loop.
More topics like this
- Best tweets about TypeScriptBrowse the best tweets about TypeScript, from type-system techniques and releases to tooling, architecture, migrations, libraries, and developer workflows.
- Best tweets about ReactExplore the best tweets about React, including components, hooks, Server Components, performance, state, architecture, releases, and production lessons.
- Best tweets about CodingA curated collection of the sharpest, most-shared X posts about coding—saved so you do not have to dig through the timeline yourself. Updated every two weeks.
- Best tweets about RustFind the best tweets about Rust programming, including ownership, async, performance, tooling, libraries, systems design, releases, and developer experience.