Hey, I ve been a software engineer (backend) for over nine years and have been wanting to build something on my own for a while now. I have ideas, good planning skills, and the discipline to execute, but unfortunately, I lack the experience as an entrepreneur, which I believe is an important aspect. This has led me to consider finding partners to help me bring my ideas to life or collaborate on new projects. However, it s been challenging to find people who are committed, structured, have a long-term mindset, and maintain positive energy. Many people get excited about a project initially, but then they disappear or lose interest when results don t come quickly. And unfortunately, I m not in a position to hire people at the moment. Has anyone else been through this? How have you found people who are truly committed to the long haul?
This came to my mind when I read about how the creation of Sora has raised concerns that it could be an AI equivalent of TikTok (critics warning it could fall into the same addictive patterns as other social platforms).
And after several messages with some people, I also noticed how I wasted a lot of time on my desktop instead of doing something productive or learning.
I recently submitted a discussion post (topic: security risk of ecosystem lock-in with password managers) and it got rejected. Went back through the community guidelines afterwards and honestly couldn't pin down which one it violated - no product mention, no promotion, no spam, just a genuine question aimed at makers and users. I am curious how others here dealt with a similar situation:
Did you appeal, and did it actually go anywhere? or Did you just rewrite and resubmit without knowing what was wrong the first time?
I am trying to figure out if this is a broader pattern worth raising with the PH team directly. Thanks for your comments and contributions in advance.
I ve noticed coding assistants sometimes suggest a library for something that could be handled with the existing stack. That can slowly add unnecessary dependencies to a project. Do you have a rule for deciding when an AI suggested package is actually worth adding?
When a team is small, it s usually pretty easy to figure out who knows what. But as the company grows, I imagine there s a point where constantly asking someone for an answer starts creating more problems than it solves.
For those who ve grown a team, when did you start noticing that shift? And what changed?
I've been active on PH for a few weeks now, mostly commenting on launches and joining discussions.
One thing I didn't expect: the feedback here is more honest than almost anywhere else.
Not because people are harsh. But because makers here have actually shipped things. They know what a real problem looks like vs a solution looking for one.
I've found that reading comments on other people's launches teaches you more about product positioning than most courses do. You see exactly what confuses people, what excites them, and what makes them scroll past.
I'd present roadmaps and projections like they were facts. Pricing decisions like they were calculated. Hiring timelines like they were guaranteed.
They weren't. They were structured guesses with good formatting.
The shift happened when I started saying "this is our best bet right now, here's why" instead of presenting everything as certain. Decisions got faster. The team trusted the reasoning more because it was honest.
I have already subscribed, am a paid customer, heavy promoted the start-up in peer groups, referred couple of paid customers. So, besides these what do I give him? Any ideas and suggestions are welcome. Budget - under $100
