> I have seen way too many startup founders delude themselves into building more and more for months without a single conversation with a real user This has been a problem since the beginning of tech startups. I worked in a dot-com in the late 1990s. Lots of investor money. New offices. Hundreds of employees. The product was well thought out, fairly well built, and it worked. But they had no customers. It's even in t…
Hence marketing in making people want it. So you have two options, be good at making people want to spend money on something. This is pretty hard and a rare capability. The other is to watch trends and catch what people want now, and be ready to deliver a product that does that....
Punch yourself in the face with reality
91–100 of 139 posts
Re: Punch yourself in the face with reality
#92Posts like this one always made me feel like I was a coward. Like there was.. unvirtuousness.. in not killing one’s darlings, not validating ideas, not quitting things in time, not looking for product-market fit.
I can report that looking for product-market fit, and everything else from the list above, became easier once I started taking antidepressants and adhd meds.
For example, it turns out deciding to punch yourself in the face with reality is much easier when you don’t feel, for example, like abandoning a project would be a giant betrayal and a thing one might in theory do but you must never do ever under any circumstances.
- - -
There are likely many people who have more capacity for self control, and who are genuinely helped by hearing moderately harsh truths because they can (1) take a look at their behavior, (2) realize it hurts them and their chances of success, (3) realize where they’ve been blind to reality, and (4) change.
I suspect that such people assume — maybe correctly in most cases — that if someone hasn’t done (4), it’s because they haven’t done enough (1-3), and this is the appropriate lever to push.
I don’t know how to finish this comment.
Re: Punch yourself in the face with reality
#93I spent multiple 5-hour sessions spec-ing my climbing app with AI, clarifying interactions, algorithm, workflow etc. It ended up a frankenstein that I didn't recognise or know how each part interact with each other. Command line were a mess, different commands doing the same thing, with similar but redundant arguments. Everything looks kind of doing what I intended but overly convoluted and nothing really works. Real…
It's very difficult to keep AI focused, when it barfs out 3 pages of reply in response to a one-sentence prompt. It's sort of its nature for some reason, it's very impressive if you've never seen it but it's exhausting to use for very long. It's like a very eager assistant who doesn't have enough experience to understand scope.
Re: Punch yourself in the face with reality
#94As someone who used to have an incredibly hard time putting my app in front of users, or asking for feedback, or getting rejected, etc: Posts like this one always made me feel like I was a coward. Like there was.. unvirtuousness.. in not killing one’s darlings, not validating ideas, not quitting things in time, not looking for product-market fit. I can report that looking for product-market fit, and everything else f…
Re: Punch yourself in the face with reality
#95Re: Punch yourself in the face with reality
#96No this isn't punching yourself in the face. Not for swes. What's written above is self confirmation that you are better than AI and that you will always have a job because you are better because AI can't build something that works. That stuff about convincing yourself you're building something useful is actually the easy question. Punching yourself in the face involves telling truths that are incredibly hard to stom…
This doesn't even match with reality. I got laid off in January because of "ai" (scare quotes because it was really about the salaries of the US based teams being more expensive than the overseas teams, I think). I got hired at a new job with better pay within two months, and my team is still hiring software engineers, and we work on cutting edge stuff. And yes we use AI (tastefully), but nobody here expects it to replace them. Hacker News and twitter are a fricking echo chamber of the most obnoxious people trying to be "thought leaders", but it doesn't match my reality at all.
Re: Punch yourself in the face with reality
#97Re: Punch yourself in the face with reality
#98> And I think that’s the biggest danger of AI. You convince yourself that you are doing something useful when you are not. Building technology to overcome relatable hardships and frictions is a worthy challenge full of meaning. Using someone else's technology to erase frictions and hardships from your life can erode meaning. On my worst days I am convinced programming and technological optimism is a theft of meaning;…
Re: Punch yourself in the face with reality
#99I spent multiple 5-hour sessions spec-ing my climbing app with AI, clarifying interactions, algorithm, workflow etc. It ended up a frankenstein that I didn't recognise or know how each part interact with each other. Command line were a mess, different commands doing the same thing, with similar but redundant arguments. Everything looks kind of doing what I intended but overly convoluted and nothing really works. Real…
Does anyone want one?
The article says to stop building and go outside!
And actually, talking about climbing apps with fellow climbers is a great way to be outside.
Re: Punch yourself in the face with reality
#100Earlier quoted context omitted.
It's very difficult to keep AI focused, when it barfs out 3 pages of reply in response to a one-sentence prompt. It's sort of its nature for some reason, it's very impressive if you've never seen it but it's exhausting to use for very long. It's like a very eager assistant who doesn't have enough experience to understand scope.
3 pages of reply or overly verbose code, often without abstractions - I read all the posters here and in other forums say that programming has shifted towards reviewing AI output rather than coding said output manually; I agree, however, I just don't buy that everyone is actually reviewing the code as intensely as one would expect - there is a tendency that arrived rather quickly to assume that the AI is correct and…
It's not different than when coding by hand, often we take shortcuts by hand that we then have to pay for later. It really just becomes a judgement call on when to stop prompting new features and start service what you have.
I think with AI and vibecoding its tempting to assume the output is good and chase the dopamine hits of more features, more features, more features, but eventually you get stuck.
That being said AI is also a great tool at paying down tech debt. It's great at helping you read a codebase and can be great at making the mechanical changes you want. And I think there is some truth to the story that newer models will be able to pay down debt (fix the slop) of older models. But its all shades of grey, newer models are better than older ones, but can I emit slop with 5.6 faster than 5.7 will be able to fix it in the future? Nobody knows.
It's not like human projects are devoid of bad code, its all tradeoffs and shades of gray. But to be honest I haven't written a line of code by hand in a while.