570 karma · joined April 30, 2025
Feels like we’re heading toward a future where ads aren't just links anymore, but part of AI results itself.
Constraints define the how and why, they shape focus, discipline, and intention.
Together, they form a system that keeps progress going.
I don’t see them as opposing ideas.
Constraints and goals work best together for most of my real-world projects.
Still a great read and interesting point of discussion.
But if not, I’d make validation your priority.
TL;DR:
Start with the problem and real users. Get a commitment, build the absolute minimum, and be relentless about learning from feedback. Three months is enough to make something real, maybe not beautiful, but definitely valuable.
---
I’ll throw in my two cents, speaking as a dev who’s been at this a while (definitely not a 10x’er, imposter syndrome still hits now and then).
If you’ve got three good developers, that’s a huge advantage. But before you dive into the building, focus on the problem, not just the product.
1. Validate the pain first. If you already have a clear problem and real demand, you’re a step ahead, just focus on a well planned execution. But if not, I’d make validation your priority. Reach out to your network or a niche you know.
Don’t just brainstorm ideas, talk to potential users and ask what actually frustrates them or what slows them down.
Example: My local gym used to distribute paper fitness programs. Challenges included managing clients' programs, tracking fitness progress and client engagement. A local software team built them a simple app, proved it worked, and is now selling that app to other gyms. That’s finding demand before building.
2. Land a real-world test partner. Critical in my opinion. If you can get a business or a group of users to commit to trying your MVP (even a rough version) as a pre-sell access, you’re way ahead.
3. Build first the smallest thing that solves the problem. Once you’ve validated there’s real demand, ruthlessly focus on those features first. What’s the absolute minimum you can build that proves value? If your MVP feels “almost too basic,” you’re on the right track in my opinion.
In three months, you won’t ship perfection, but you can absolutely deliver a working, usable V1.
4. My own experience: Right now, I’m working on a SaaS for a niche industry. I partnered up with a company, went to their annual conference, and spoke with managers about their biggest headaches. After presenting a mockup built over a weekend, I proposed a free plan to a pilot group (50 users) in exchange for honest feedback, and made it clear that we’d refine it before moving to paid customers.
I’ve spent about six months on it (part-time, mostly solo dev, with two part-time teammates handling design/support). We’re about to launch it to the pilot group. The whole thing only worked because we started with the problem, not the tech.
5. If your goal is $1k/mo in SaaS revenue within 3 months, you’ll need a real buyer lined up from day one, but it’s possible.
For a YC interview, I'm far from that ecosystem but I can only assume it’s similar to pitching to a potential client. For me, it's always been about solving a clear issue and showing progress.
Fundraising? Same as above, you’ll need to prove users actually care about your product even if it's minimal and rough.
For me, the biggest wins came from real user validation, listening to feedback and fast execution. 3 months totally possible!
Hope your hypothetical turns into something real, and worthwhile, in three months or less.
For example, I always believed ostriches buried their heads in the sand to hide, turns out I was naively wrong.
From wiki page:
Ostriches do not stick their heads in the sand to hide from enemies or to sleep. This misconception's origins are uncertain but it was probably popularized by Pliny the Elder (23–79 CE), who wrote that ostriches "imagine, when they have thrust their head and neck into a bush, that the whole of their body is concealed".
Thanks for sharing.
YouTube is full of tutorials that can help you get started, but the real shift for me happened when I stopped planning and just hit publish. My first video is rough and super amateur, but putting it out there felt empowering. It made me want to keep going.
I’m no expert, but one thing’s clear is that you only get better by doing. Tutorials help, but nothing beats hands-on learning.
In my case, I’ve always liked Casey Neistat’s raw, authentic style. I’m still working up the nerve to get in front of the camera more, but I know I’ll get there.
I know my comment might sound a bit off-topic since you’re asking about the technical “how-to”, but that’s kind of my point. Don’t get too bogged down too much in the setup. It can keep you from ever starting. Once you begin, the tools and improvements tend to come naturally.
Good luck, and honestly, just start.
Looking forward to seeing your videos.
I think it's a good sign that you're reaching out for help and advice. That shows a level of self-awareness that’s important when dealing with burnout. Of course, I’d strongly recommend speaking with a medical professional or therapist, especially if it starts affecting your day-to-day functioning. But I’ll share what helped me personally.
I went through burnout after working nonstop on a project for over six months, only for it to be shut down two weeks before launch, for reasons completely beyond my control. It hit me hard, but I didn’t realize it right away. It crept in slowly, a lack of focus, no motivation, no excitement, just a kind of numb disengagement.
Here’s what helped me:
Acknowledging what I was going through was the first real step forward. Just putting a name to the experience gave me a bit of clarity.
I started reading books about stress, burnout, and anxiety. Not because one book had all the answers, but because the act of engaging with helpful material gave me structure and a sense of progress. I also read lots of fiction to change my mindset.
I talked to close friends and family. Just expressing how I felt, especially about the project, helped release some of the pressure.
I experimented with small activities that felt even slightly interesting. That varied day by day. Some days I journaled, other days I took longer dog walks or spent more time at the gym.
Recovery wasn’t linear. It wasn’t fast. But creating space to decompress and explore what helped me, even in small ways, eventually got me going again.
One important thing I learned is that burnout doesn’t go away with a single solution. It’s not like taking a pill for a headache. It took time, reflection, and consistent self-care. For some, professional support may also be a key part of that.
So my best advice is: Don’t pressure yourself to “fix” it overnight. Stay aware, try things that feel nourishing, and don’t hesitate to ask for help.
Of course, everyone’s experience is different. If it feels overwhelming or doesn’t improve, definitely reach out to a mental health professional. You don’t have to figure this out alone, support is out there.
Sincerely hope this helped.
I knew about toxic wallpaper, but hadn’t turned the page on poisonous books. (Apologies for the pun. I’ll see myself out.)
But in all seriousness, I’m glad to see efforts like this helping to identify and prevent potential harm.
In my case, I avoided interacting with social media for most of my life. No Twitter, no Facebook, and until recently, not even HN (aside from reading). This was to protect my focus, and my attention span. My smartphone was just phone.
But I recently started a creative writing practice, and sharing ideas has become important to me. HN felt like a safe place to engage, and I genuinely enjoy the discussions here. That said, I’ve already noticed myself checking my phone more often, anticipating replies, and chasing that little dopamine spike. What was once just a phone is now a catalyst for distraction and creative connection, all at once.
I’ve held off posting to platforms like X because I suspect it’ll get worse. But in today’s world, where writing or building anything online often means “building a following,” is it even possible to avoid the trap?
Are there meaningful ways to engage and grow publicly without becoming trapped in doom-scrolling, infinite feeds, and notification loops ? Or is distraction now the entry fee for visibility?
Would love to hear from others who’ve tried to strike this balance, especially writers, developers, and indie founders.
It reminds me of a recent conversation I had with a friend who went on a family road trip and decided to turn the ride into a Spanish practice session for the kids. Seemed innocent enough… until they started using an AI chatbot to help with translations.
At first, it was helpful. Then it got creative. Very creative.
Suddenly, “Where is the bathroom?” became something like " follow the dark path to the eternal chambers of mystery" “And “Please pass the salt” morphed into something about offering sacred minerals to the goddess priestess.
Needless to say, I strongly advised them to stick to Google Translate next time. Sometimes you want a translator, not a hallucinated poet on your road trip.
Thanks for sharing.
But then I paused. I thought, surely with federal urgency and resources, they had access to advanced internal tooling or some supercharged AI product. This is sensitive work, impacting essential services. It would require deep domain knowledge, careful oversight, and rigorous review. I imagined a team of 10x engineers and policy analysts coordinating a finely tuned system.
After reading this piece, I realized my original suspicion was correct, but the reality was worse. No secret AI. Just a general-purpose model, with vague prompts, limited contract context, and questionable assumptions. That they didn’t anticipate hallucinated figures or misclassified services is frankly baffling.
Even with my limited AI experience, I would have known these risks. And that’s the real concern: not just flawed execution, but a fundamental misunderstanding of how and when these tools should be used.
It makes me wonder how many other organizations are deploying LLMs in the same way, unproven or experimental systems driven by deadlines, with little grasp of the underlying complexity or consequences.
At the same time, I can’t help but think about calculators. I know it’s a primitive comparison to what we’re dealing with today, but in some ways it’s still relevant. People once worried calculators would kill mental math. Debates were endless and sure, maybe we did lose something, but we also gained a lot. We adapted.
What feels different now is the speed. AI is moving fast and hitting every industry at once. Some are diving in, others are holding back, and most people are somewhere in between, trying to keep up while figuring out what it means for their work, their kids, or their creativity.
I do worry about the younger generation, especially those growing up with this tech baked into daily life. If AI ends up doing the thinking, writing, and problem-solving for them, how will that shape their ability to reason, learn, or build original ideas?
To me, the real challenge isn’t AI itself, it’s the pace of adoption. It’s simply outpacing our current education systems and frameworks for developing human skills. So I get why it feels threatening. It’s not fear of the tool, it’s fear of what gets lost if we skip the part where we teach people how to use it meaningfully.
That’s why, at least for myself, I try to see it for what it is: a powerful tool. As someone new to blogging, I approach it the same way I’ve approached my IT work, use the best tools available, but don’t forget the purpose. I still want to write in my own voice, to work through ideas and get better at expressing them. If AI can help sharpen that process, that’s great. But it can’t do the work for me.
The post was more about the hype and attention surrounding AI, which can feel mentally exhausting at times, mostly because of how fast everything is moving. Not a complaint, really. If anything, that might be a good sign. I totally get why people are excited, it just takes effort to stay grounded in the middle of it all.
Appreciate the comment! Hopefully next time I’ll be jumping in with war stories instead of sideline takes.
In my case, not always, but often, procrastination shows up when fear is involved. Fear of failure, of not doing something perfectly, of the task being too big. What’s helped me is turning the task into a challenge, because I know that personally, I thrive on challenges. It re-frames the fear into something exciting, and once I get started, I follow all of the other advice such like breaking it down into small steps. Thanks for sharing.
I’ve lost count of how many times I’ve had to explain, again and again “No, AI can’t do that… and no, it’s definitely not drawing up your architectural building plans.” Well, not yet, anyway.
My dotcom comparison wasn’t really about the tech, more about the noise and hype. Feels like that same kind of frenzy, but now the tech’s actually capable of doing something big. The financial viability is still a big question though. Thanks for the comment.
But surprisingly? What I’ve been most excited about lately is my blog.
And please don't read this as a shameless plug. I just like to encourage others to try if they are thinking about it. A space where I share thoughts about anything and everything. Surprisingly, it’s been a great mental reset and creative boost for my coding work during the day. It’s helped more than I expected.
Good luck to everyone with their projects.
What stands out to me right now is just how loud the expectations around AI have become, especially among non-technical folks. It’s not just “Bitcoin hype” loud, it’s bordering on “AI will solve everything” levels of noise. For those of us who’ve been around a bit longer (sorry, younger HN crowd), the current buzz feels reminiscent of Y2K or the first dot-com wave.
Back then, I was early in my career, but I vividly remember the headlines, the overpromises, and the sheer volume of attention. The difference now is, there’s a lot more substance under the surface. The tools are genuinely useful, and the adoption curve feels more practical, even inevitable. That’s what makes me think AI might become to this era what the smartphone was to the last, not just a novelty, but an everyday dependency.
That said, I’ve also learned a lot from voices here on HN, especially when it comes to the financial realities behind the tech. If there’s one throughline in many of these discussions, it’s that financial viability, not just hype or innovation, is what ultimately determines whether this all collapses or truly transforms the world.
Just my 2 cents.
I’ve been toying with the idea of jumping on the content creation wagon with storytelling, vlogging life experiences, that sort of thing, but now I’m wondering: Is it still worth building on YouTube if there’s a real risk of getting banned later for unknowingly crossing some unclear content line?
I’m not focused on monetization right now, just hoping to share and connect, but I’d hate to build something meaningful only to watch it vanish overnight.
Exactly the kind of case study I was looking for to share with a business client.
Thanks for sharing!
It definitely will never be a replacement for HR or top executive thinking. At best, I’ll be proposing something much lighter, more like a glorified internal search tool for real user examples. To be honest, I’m still all figuring it out. Best case: a helpful resource guide. Worst case: it adds no real value.
The tricky part is, if I don’t provide something, even just a prototype, they’re already looking at other consultants who’ll happily promise the moon. And that’s my bigger concern: if I’m not involved, someone else might introduce a half-baked solution that interferes with the SaaS I’ve already built for them.
So now I’m in a position where I need to put together a clear, honest demo that shows what this tech can and can’t do, just to avoid further complications down the line.
Ironically, this all started when another “AI expert” sold them the idea.
I’ve been saying the same thing all along, we’re not quite there yet. Maybe one day, but not now.
I also get that businesses want to take full advantage of this tech when it’s pitched as a money-saving opportunity, the pressure to act fast is real.
I wonder how many other devs and consultants are facing similar situations?
That said, I don’t think it quite echoes Echo (that pun might be intentional) or maybe it does, financially speaking.
For me, this wave feels different: deeper integration, broader scale, and real-time utility. I agree, if the returns don’t hold up, a major correction isn’t off the table.
It reminds me a bit of the smartphone era, rapid adoption, strong dependence. I guess, the difference is, that phones had clear monetization paths. With AI, we’re still betting.
The bigger question for me is, if this all collapses, what happens to the workflows and investments already built around it?
Thoughtful post.
This might be a total tangent, but every time I see “newts”, I think about how Karel Capek actually coined the word robot in his 1920 play R.U.R., and then later gave us War with the Newts...really smart amphibians. Thanks for sharing.