When i first started using productivity apps I thought i d stick to one simple system and never overcomplicate it.
A while later I somehow ended up with different apps for notes tasks reminders and random ideas. Some of it is useful but sometimes I wonder if I m just creating more work for myself. How do you tell when your system is actually improving versus just becoming more complicated?
When I first started building things I thought adding more features would always make the product better.
Then I realized every extra feature also adds more decisions suppor and things that can break. Sometimes the hardest part is knowing what to remove. How do you decide when a product needs more features versus when it just needs to be simpler?
In a discussion forum with @monatruong_murror , we talked about how AI can help us learn things that aren t naturally familiar to us, like programming.
The biggest challenge was/is: Getting AI to guide you toward a solution, instead of just giving you the answer.
But companies are still opening internships, which suggests something deeper than just skill-building still matters (like understanding systems, workflows, and how companies actually operate the management part).
Apple's latest event is tomorrow. They are expected to launch brand new iPhones, an Apple Watch pro maybe and maybe some new Mac drops What do you want to see?
We are a venture firm, not a software company. But when we need a tool now, the first question is not what to buy, it is whether we can just build it ourselves. A few subscriptions we used to renew without thinking are gone.
Curious what others are seeing. Have you cancelled anything because you built the replacement, and did it hold up?
Half of what I ship is a crawler, and the failures I dread are the quiet ones. A company moved its careers page to a JS widget last month, our parser kept returning HTTP 200 with an empty list, and from the outside it simply looked like they had stopped hiring. Nothing alerted, because technically nothing had failed.
I ended up alerting on the shape of the data instead of the status code: if a source drops more than half its rows overnight, a human looks at it before anything downstream moves. That threshold is a guess, and it still misses the slow rot, where a site changes one selector and you lose a third of the fields without ever losing the page.
The Product hunt community is amazing, and I know there's lots of knowledge to share. I want to make the forums the most vibrant forums for product builders on the internet! To that end we've re-designed forums, defined sub-forums, and introduced product-specific forums, and we've drafted new guidelines to keep the discussions vibrant, authentic, and genuinely useful. The new guidelines are here - https://help.producthunt.com/en/... - you can read them in full, but here's my summary: When posting a new forum thread, ask yourself:
1) Is this a genuine question I have that I want the community to answer? 2) Is this an insight that will be helpful to other builders and product geeks?
Today I celebrate a big milestone. 365 days in a row active on Product Hunt. Honestly, quite a number given how many things happened in my life this year, it feels like I could write a book about it.
But consistency takes effort. Here are 3 things that helped me:
