A two minute check for anyone who lets a script, a CI job or an agent run commands in their repository. List the commands that ask before they do something. Then find out what each one does when nobody is there to answer.

Mine is the schema migration generator. Its job sounds like writing a file: compare the models against the database and produce a migration for the difference. To compare honestly it needs the database up to date, so if any migration has not been applied yet, it asks whether to apply them now. The default is yes.

Nobody reads that as dangerous, because there is a question, and the question is the safety. There is a second safety underneath it: the console framework checks whether it is attached to a terminal, and if it is not, it marks the run non-interactive, and a non-interactive run refuses instead of applying anything.

I read the code this morning to find out why neither of those had ever stopped it. The terminal check only runs if the input object has a stream to test. The ordinary input, the one built from the command line arguments, has none. So the check is skipped, the run is treated as interactive, the question is asked, and reading the answer hits the end of an input that was never connected to anything. The library treats end of input as no answer, and no answer as the default. Yes.

I've tried both and I'm still not sure which I hate less.

The all in one approach is nice because everything is in one place. Notes, tasks, docs, databases, whatever.

Then eventually the app starts doing so much that I feel like I'm managing the system instead of actually using it.

So I split everything up again, end up with six different apps, and then complain that everything is scattered.

I started skipping the review section and going right to the comments. Most reviews sound identical after a while, full of generic praise that tells you nothing about how the tool actually performs.

The comments are messier, but people mention real issues like bugs, missing options, and setup friction. That input is far more helpful before testing something new.

Where do you find honest signal on a new launch? Do you read the comments, rely on recommendations, or just test the app yourself?

The thread on when to launch got me thinking about what happens right after.

In the past, I launched product via Reddit and not PH. One that I did on PH was a dead one. We launched a fintech product a few years back and it went well (through Reddit though)! 100+ signups in about 72 hours. I have never felt more like a founder than I did that Tuesday.

Then Wednesday arrived. Two of us, both technical, trying to have 100 conversations while also fixing everything those 100 people were cheerfully breaking. We got to maybe 20-30 properly. The rest got a welcome email and then a long, dignified silence.

Hey Product Hunt,

I m curious for those of you who ve done it (or are doing it), how did you launch a SaaS without a tech background?

What tools, tips, or strategies helped you make it work?
Did you use no-code, hire devs, or partner with someone?

We've spent almost two years building an e-commerce platform, and we're now facing a decision that I think many founders eventually run into.

Do we keep it closed-source and build a hosted SaaS business around it, or open-source the platform and try to build a community around it?

Last night I was still working at 1AM. Everything I actually meant to ship was done by six. Then I kept going and generated a few sets of slides for my next PH launch. 

Two years ago, I would have ended by eight. Not because I had more discipline - because I would have needed a designer, needed to wait on my devs. The day ended when I ran out of things I was capable of doing alone. 

We were picking a CRM for the studio, and I went down a hole. Ended up reading about 180 reviews of the best-funded tool in the category. $116M raised, most of it this year. G2, Capterra, Trustpilot, the app stores, a pile of Reddit threads.

I expected the complaints to be about missing features. Nope.

When mass layoffs started in tech, many people suggested that:

1. The layoffs were happening because, during COVID, companies hired too many people for online and remote roles.

2. That AI was attacking jobs.

And I still keep seeing statements from creators of various AI tools saying:
No, AI won t replace you. Employees will just have time for more meaningful tasks in a company.