Hacker News Reader

Lovely language / solution mismatch.

Any compiled language would fit this much better - fail at compile time. Or in interpreted-o-world, at least do it at test time.

I guess it's just lovely when deployed, working, test-passing software suddenly starts failing on a server (all servers at once, globally), because someone added a TODO a few weeks ago.

View on HN

From the README:

"In your production environment, set DISABLE_DO_BY=1 to disable checks."

Given that we are talking about lazy/overworked on top of lazy/overworked here, why any confidence that this will be done 100% of the time?

Putting time bombs in your code, regardless of a global configuration switch, is just asking for trouble.

You're correct, I'm going to change it to be disabled by default.

I agree with you; my point was that while skrebbel spoke as if the point had never even been considered, it had in fact been considered.

I have to admit to a certain amount of pet-peeve-like sensitivity to people commenting in ways that make it look like they only read the title.

I am guilty of this more often than I care to admit. Ooops.

Reply on news.ycombinator.com