shivaniShimpi_

without ranking or algorithm how do you ensure folks would see relevant posts up top? it could lead to a lot of noise / spam

i've stopped using google since forever now, i love how claude in terminal spoils me w websearch and stuff :P tbh if you come across some good SEs, i'm open to suggestion. tried dia for a bit but that's a bit of an underkill

hear hear!!!

i didnt realize i needed the volume scaling with tokens burned as much as i do now xD imagine the screaming when it confidently refactors something for 40k tokens and then finds out the thing it deleted was load bearing

the solution awareness problem is real and honestly undersold as a challenge. you spend half your energy explaining why someone should practice a skill before they're in the situation, not just selling the product itself. would love to compare notes, checking out getsimul now

this is the right frame. i'd add one layer though, the architecture itself is built from user understanding that compounds over time. every conversation with a user, every weird edge case, every "wait why did they do that" moment is load bearing. someone copying your product on day one is copying a snapshot of what you knew then, not what you know now and then by the time they ship their copy you've already moved. the gap isn't the code it's the accumulated context about why the code is the that it is

the execution vs idea debate always felt like a false binary to me. bad idea executed perfectly is still a bad idea. but also a great idea with zero distribution instinct goes nowhere. your comment made me think about is that most founders who say "ideas don't matter" had a good idea and dont realize it because prolly they were too close to it

the begging thing is a bit of a myth imo. what it actually looks like is you describe the problem out loud to someone and they go , god yes that's exactly it - before you've even mentioned a solution. that reaction is the signal. you're not manufacturing demand you're just finding where it already exists. the hardest part is you need to talk to a lot of people before you find that reaction, that was the biggest pitfall i fell into during my first startup. trying hard not to make the same mistake twice, youve to be really mindful

the vibe coding point is the one nobody's saying out loud enough. it doesn't just make building faster, it makes the gap between "i have a thing" and "i have a business" feel smaller than it actually is. you ship in a week and it works and you think you're close. you're not, you just moved faster to the same hard problem the distribution bit is where we are right now honestly. talking to users before writing most of the code was the one thing that changed how we think about it

the feedback loop point is exactly it. flight simulators work because every decision gets immediate feedback. most real life skill practice has the worst feedback loop of all, sometimes you don’t find out you negotiated badly until years later. that’s what we’re trying to compress