Hacker News new | ask | show | jobs
by mercenario 293 days ago
I dont agree.

> This may be stored as a boolean column, is_confirmed, in the database. It makes a lot of sense. But, you're throwing away data: when the confirmation happened. You can instead store when the user confirmed their email in a nullable column.

When I'm looking at a database schema and I see a boolean is_confirmed I can be 99% sure what it means. Now if I see a datetime confirmed column, can I be sure that if I want to know if it was confirmed this will not be null? I'm definitely not 99% sure anymore and I would be scared of making this assumption in my code. Obviously I would still think I can use, but going from 99% sure to 80% sure is a recipe to making brittle code.