karparov

Discussing is obviously fine.

But sometimes some innocent blog posts get criticised as if they claimed that they solved world hunger. They don't. They are often just some random thought in a rarely-read blog. Nobody intended to go convince a gang of seasoned hackers that they have undisputable wisdom.

It takes more than a few minutes, yes. But this one-time investment will prevent the next 10 migration-related bugs that he'll otherwise blog about.

Grab some representative data from production and keep feeding that into your migration tests. Keep updating those. Worth each minute if you care about quality.

Pre-populate the db.

Tbf, it's not their fault it made it to the HN front page.

Are we going to criticise every little innocent blog post just because somebody liked it, submitted it to HN and it got enough upvotes?

> This wasn’t caught by the existing test suite (even though it runs almost 200 end-to-end tests), because it always starts from an empty database, applies all migrations and only then runs the test code.

Isn't that where the test coverage has a hole?

I somehow expected the blog post to extend testing for this. A pre-populated database which is then migrated. That seems to catch a wider class of issues than parsing sql and shielding against just checking for non-null without default.

Twice a year? That's only recommended by dentists in north america because most insurances cover it because of lobby pressure. Every 1-2 years fully suffices, depending on your risk profile (smoker, genetics, ...). That's what countries where the insurrance doesn't have skin in the game recommend.

And the average european has much better tooth health than the average u.s. citizen, in my experience.

Or just not consume any water.

As a random US citizen, chances are high though that you voted Trump and are ok with all this nonsense. So, should be ok?

As a European who has lived in both countries I can only laugh at this. From our perspective, US and Canada are 99% identical, culturally.

It's also restricting the freedom of communities if you ban them from adding fluoride to their water if they like to.

This ban is anti-freedom. (Just like forcing them could be argued to be, even though that's what you argued against.)

So, this ban is arguably reducing freedoms on multiple levels.

"Receive messages on Signal via a simple API. Perfect for notifications and alerts." is not "how it works" but "how you use it".

This is "hacker news". A hacker is typically interested in how something works (under the hood).

If a hacker asks "how does this mobile phone work?" then they are not looking for "well here you press a button and then here you speak" but something about radio waves and cell towers and mobile operating systems.

> > Who is behind this

> SignalBot − built by gwillem © 2025

When I looked, this information wasn't there. Only the "buy me a coffee" link. Now it is, thanks.

"... seeking the truth ..."

Hahaha, ha ha, ha...

Maybe more accurate to say "spreading my truth".

You built this? Would you like to comment what your future plans are?

Your self-description is "entrepreneur love for automation". Is it fair to assume that if this takes off then you are planning to introduce paid plans (perhaps with some revenue sharing with the signal folks to lift rate limits for you)?

Who is behind this and how does it work?

Why is this information not present on the front page?

And why does somebody who thinks people would start using and relying on it not immediately understand that that's important information?

> Damn, local LLM just made it up.

> I just searched for the quote and my comment shows up as top result

Welcome to the future. Isn:t it lovely?

And shame on you (as in: HN crowd) to have contributed to it so massively. You should have known better.