Thomas Langhorst

@jonathanbrnd As an engineer learning how to market I think I am too biased to answer this question 🤣

who wins? 1. a cracked marketer learning vibecoding 2. a cracked engineer learning marketing

Big lesson while building my AI-for-devs guide: Setup > prompting. AI isn’t inconsistent — it’s stateless. Every new chat starts from zero. Persistent context changed everything. Building this in public.

@shiri_shh Finally someone who acknowledges my skills 😂

dear algo please only show this tweet to S tier programmers

One simple step reduced AI mistakes for me and my team: We stopped over-specifying. Instead of: "Create a service, add this endpoint, use these functions, follow these steps…" We used: "Add an endpoint that follows our auth pattern and matches existing error handling."

You need this if you use AI on a real codebase: One shared instructions file. Little known fact about what to put in this file: - Architecture decisions. - Conventions. - What NOT to do. It's onboarding for humans *and* AI!

@chhddavid Keep grinding man. I wish you all the best. You deserve it!

day 143 of building in public MRR: $5.3k Goal: $10k still working hard on gathering templates. i've made some myself, with a mix of what other people have built so amazing to see what Shipper can do! goal is to pick the most beautiful and functional apps so that the 1st impression is "wow this tool can actually build cool stuff"

@starter_story Good advice! Thanks for sharing. I find it hard though. I have a gazillion posts und mind, but none of them work. What do you think works best: sharing mistakes, accomplishments or just simple advise from “today I learned”?

tl;dr You should do cool, tangible things, and share them. Most people on X post recycled advice or ChatGPT slop. None of that signals progress or competence. It’s abstract and forgettable. There’s no reason to follow someone who isn’t actually doing anything. AUDIENCE GROWTH COMES FROM VISIBLE OUTPUT Additioanlly: progress, mistakes, and experiments feel real, and people connect with that. It also lowers the fear of posting. The reality: no one is really paying much attention to you; they’re focused on themselves! Thanks @jackfriks for the awesome interview!

$20K MRR founder shares what most people get wrong about "building in public":

@MakadiaHarsh So true! Getting up at 4am because the server crashed … this is what most people don’t have in mind when they hear “ship fast, iterate”

The "ship fast, iterate" playbook works, but most founders skip the unglamorous middle. The daily user calls, the constant feedback loops, the obsessive focus on actual problems before they even think about scaling. You can ship an MVP fast. You can get interest, a waitlist, even early revenue. If your product is simple or you have basic product instincts, sometimes you really can build and validate something meaningful quickly. It happens. But most of the time real products still take months. They need iteration, debugging, new features, and actual users so you can test and fix. Non-technical founders often miss that products are living organisms. They need maintenance, they need oxygen (distribution and retention), and none of that is instant or one-time work. Anyone claiming you can automate user research is lying. Anyone promising product-market fit in 2 weeks is selling an edge case. These outcomes happen, but they're rare and treating them as the standard is how founders end up burned out and bitter. A lot of the "just ship it" advice comes from comparing today to the 2000s/2010s, when companies were built with decades in mind. Too many founders now fantasize about quick wins instead of deep user understanding, largely due to X and very largely due to every guru jamming the "launch in a weekend" narrative down our throats. I'm not saying you shouldn't want to move fast. That's actually exactly what i prefer. You might see more success by aiming for user connection first because the opposite is a very unlikely-to-hit gamble where you only see the wins on your feed. Do not let X convince you that shipping fast means skipping the conversations or that 10k users in a month without talking to any of them is normal.

@casinokrisa @alexcooldev So true! I am able to fix bugs in minutes now, but I know exactly where to look and which routes to neglect. Knowing how to code gives me the unfair advantage

@alexcooldev Vibe-coding works until it hits scaling or debugging walls that require solid fundamentals.

To be honest, I'm also vibe-coding 80–90% of all my projects. Vibe-coding feels amazing when you actually know how to code and understand how the system works.

@alexcooldev Absolutely! I feel like I have a junior dev doing all the work while I get to do the cool parts 💪

I learned this the hard way: I always expected Copilot to *remember* things. It doesn't. If it’s important, it belongs in an instructions file — not in last week's chat. Let Copilot update your instructions files regularely.

Small lesson I learned the hard way: Generic AI instructions make output worse, not better. Specific rules > more context. Once I stopped saying "follow best practices" and started saying "use Zod for type validation, see file <path_to_file>", AI finally became useful.

Most teams misuse AI because they confuse context with instructions. Context = what AI knows Instructions = how it should behave Once I separated the two, hallucinations dropped fast.

@alexcooldev So true! This is why I have a daily power hour. I build or create something for at least 1 hour a day. This keeps me rolling, no matter the mood or motivation.

Stop overthinking. Build something. A site. An API. A messy MVP. A Chrome extension. An AI agent. A tiny automation. Momentum changes everything.

@corbin_braun Totally true! I build a while MVP application in under 2 hours. Before AI, this would have taken me at least a whole weekend

you can build anything now the only gap is time and knowledge AI is your workforce

Most engineering leaders worry about AI adoption. Here's a mindset shift that helped me: Don't tell devs to 'use AI more'. Instead, suggest moments in their workflow where AI creates instant relief. Relief → trust → adoption. It's never the other way around.

@cleanwithmike I am still working a 9-5, but I still started doing this. Now I get to spend time with my wife, enjoy nice walks and play video games, while AI + automations (+ a few own written software pieces) do a lot of work in the background.

Step 5: Bought back my time. This is the step most people skip. Making money is great. But if you're working 60 hours a week, you've just traded one prison for another. I spent 9 months finding the right virtual assistants and building systems.

I’m 32 & make $40k/month… But 4 years ago, I was: • Lost • Broke • Anxious Here are the 5 steps I took to reinvent myself (so you can too):

@hayesdev_ Thanks for sharing! I now know what to watch for my coffee break 😅

@JulianGoldieSEO This is pure gold. Thank you so much for sharing!

This update quietly changed coding forever. Here’s the new flow ⤵️   1. Install Chrome DevTools MCP   2. Connect Cursor or Claude or Copilot   3. AI launches Chrome   4. AI inspects DOM + console   5. AI fixes and validates bugs No screenshots. No guessing. Save this video, you’ll automate debugging. Want the SOP? DM me. 💬

@andi_losing Optimizing the wrong thing is always a lingering danger. Glad to hear you overcame this 💪

I made a lot of mistakes in the past weeks I wasted days setting up my own VPS I wasted days switching to Supabase I learned a lesson I should optimize my shipping speed, not my tech stack