Simran Malhotra

@csaba_kissi idea to running code in mins, idea to correct code still takes as long as it always did - maybe longer coz now you're also reviewing someone else's work on top of your own

AI shortens the distance between idea and running code, not between idea and correctness. I see this a lot when I check the generated code.

@trikcode the it's over posts are the worst part - half of them are about the same thing framed 6 different ways and none of them are actually actionable. at some point logging off is the most productive thing you can do

There’s a new kind of burnout now. Not from working too much. From trying to keep up with tools, models, frameworks, launches, and 600 people saying “it’s over” every morning.

@seraleev and the ones that work are rarely the ones you were most excited about - the app you built in a weekend outlives the one you spent 6 months on. you only know in hindsight

The hardest part of app business: You don’t know which app will work. So you keep building.

@nia_thinks before: slow and expensive. after: fast and cheap. the thing that didn't change: whether anyone actually needed it. speed just means you find out sooner

Before vibe coding: – 6 months to ship – $30K spent on developers – 3 pivots before launch – still not done After vibe coding: – idea on Monday – live on Friday – real users by the weekend the speed changes everything.

@shredandship the identity shift matters here - I'm a developer feels threatened by AI, I'm a builder just sees a better tool. same person, very different experience of the last 2 years

Some developers fell in love with writing code. I fell in love with building things. That’s why AI doesn’t feel like a threat to me. The how has changed a dozen times over my career. The why never has.

@addyosmani which means bad taste at 10x is just faster bad decisions - the people who benefit most are the ones who already knew what good looked like

AI doesn't replace taste. It multiplies whatever taste you already have.

@boringmarketer vibe coding is you steering the AI. engineering with agents is you setting the destination and trusting it to figure out the route - completely different relationship with the output

There’s a massive difference between vibe coding and engineering with agents

@Prathkum that's actually the dangerous part - every other tool fails loudly when you're wrong. AI fails quietly and keeps going, which means you ship the mistake instead of catching it

AI is the only piece of tech that does not make you doubt your skills. You build with confidence and even when you are wrong, it says "you are absolutely right."

@Akasheth_ email delivery and payment failures are the ones that hurt the most coz they're invisible until a real user hits them - you can ignore auth edge cases in testing, you can't ignore someone not getting their receipt

vibe coding a product feels easy Until you deal with: > auth edge cases > security gaps > tangled workflows > context limits > email delivery issues > payment failures that’s where you wish you didn’t skip the basics.

@Jagadeeswarrrr looks like confidence from outside part is real - ppl see the shipping and assume there's a roadmap behind it. sometimes the roadmap is just "ship this, see what happens, repeat"

People underestimate how many founders are just learning in public No master plan No secret strategy Just shipping things, seeing what breaks, and fixing it From the outside it looks like confidence From the inside it's mostly curiosity

@stjernepat43699 and it's making undisciplined builders confidently wrong - the output looks finished even when the thinking behind it isn't

Honest AI take: it's not making average builders great. It's making disciplined builders fast.

@Priya_Upadhyay_ the bugs aren't even the worst part - it's the code you can't debug because you didn't write it and don't fully understand it. AI writes fast, comprehension doesn't come with it

Many developers now use AI daily. It saves time, but blindly trusting AI code often creates more bugs later.

@Prathkum the gap this creates is real tho - building without understanding syntax means most ppl can't debug what breaks or explain what they shipped. faster to start, but the ceiling hits sooner

Then: you learned syntax before you could build anything. Now: you build anything before you fully understand the syntax.

@oranahh they'll actually defend it to others - it's expensive but worth it is the best sales line you'll never have to write yourself

When people trust your brand, they won't question your price.

@russellbrunson and better customers refer others like them - the compounding goes in very different directions depending on which end you start from

Lower prices attract more customers. Higher value attracts better ones.

@alexcloudstar the only time users notice the stack is when it's slow or broken - everything else is invisible to them, which is the whole point

Harsh truth: Your users don't care about your tech stack. They care about their problem getting solved. Rails, React, Vue, vanilla JS? Pick whatever gets you from idea to solution fastest.

@Prathkum cs is actually more relevant now - you need to understand systems, tradeoffs, and why something fails at scale to work well with AI. the ppl who only knew syntax were always the more replaceable ones

People saying computer science is dead because of AI are usually the ones who think computer science is just coding.

@AlexEngineerAI at least now there's something else to blame

Devs acting like they didn’t write slop code before AI. 🤡

@samreenn2525 and the progress posts that actually land are the ones where something went wrong - a failed experiment, a pivot, a number that didn't move. that's when ppl actually trust you're being real

Most people think building in public is about showing success. It’s actually about showing progress.

@heyblake the third one kills more deals than the other 2 combined - ppl can believe in the problem and the solution and still not buy coz they're not sure you specifically can pull it off. that trust gap is the hardest to close over a deck

People buy when they believe three things: The problem is real. The solution works. You can deliver it.