Honestly ai tools are great for knocking out a fast first draft or getting a site layout up in an hour. But as soon as i need to tweak small styling details or fix minor bugs, I have to jump back into normal code. feels like ai gets you 80% there but that last 20% takes traditional dev work anyway. Curious how you guys balance both without making a mess of the codebase?

Posting updates every single day sounds great until it starts eating into your actual building time.

Spending an hour daily tracking follower counts or numbers often takes focus away from fixing bugs or making the product better.

Plus taking a step back from constant posting doesn't seem to hurt credibility or lose users like many fear.

Have you noticed any real sales coming directly from building in public or is it mostly just noise?

I always thought having a cheap entry level plan was necessary to catch hesitant buyers. But after struggling with flat sales despite copy rewrites removing that budget option was what finally worked for us.

Instead of boosting signups the cheapest tier was just acting as a safety net that kept users from choosing the product version that provided real value.

Curious if other founders have experienced this did removing your cheapest option helps or hurt your overall revenue?

The part about password managers nobody really talks about is how often something goes slightly wrong.

Autofill doesn't show up. A website has a weird login form. You re on another device. You have two accounts for the same service and the manager picks the wrong one.

None of these are huge problems, but together they make the whole thing feel more complicated than it should be.

I m probably due for a clean setup instead of whatever combination I m currently using.

As the only one who works on my product at this point in time, I've had a habit of neglecting all sorts of documentation for ages. I was familiar with my product well enough not to get lost in details and to know what was going on and why. But after a two-week break, I couldn't recall some of my own decisions regarding a particular aspect of development.

Now I make myself take a minute or two to leave comments to any decision I've made that wasn't obvious enough, so that I won't have to go through the commit history each time I return to it. It's already helped me save some of my time.

Six weeks into developing a customizable reporting dashboard which looked cool in the demo and got the biggest buzz amongst beta testers when interviewed, usage stats after three months revealed that less than 2% of active users ever accessed it.

In the meantime, our users needed a minor tweak which would allow for exporting a table into a CSV file format which took us about a day of contracting work to implement. Now, a third of our active accounts use it on a weekly basis.

Scrolling through today's launches, it feels like half of them are AI agents now applying to jobs for you, editing your videos, handling outreach, monitoring other agents. Some of it genuinely saves hours. Some of it I still want to keep my hands on.

So I'm curious where everyone draws the line.

I've noticed a growing undercurrent of people wanting real ownership over their digital data, their photos, notes, bookmarks and media, rather than renting access to it from a platform. Sony ending physical disc support on their next console reinforced this for me, since it's another case where you own less of what you paid for and control less of it too.

At the same time, people generate more personal data every year, and NAS and self-hosting tools have never been more capable than they are right now.

So I'm curious what this community thinks. Is there a real path for a genuinely consumer friendly self-hosting product, something as easy to own as a router, to actually go mainstream? Or does the setup and maintenance overhead mean this stays a niche for people who enjoy tinkering, no matter how good the software gets?