Hacker News: chikinpotpihttps://news.ycombinator.com/user?id=chikinpotpiHacker News RSShttps://hnrss.org/hnrss v2.1.1Sat, 27 Jun 2026 02:33:24 +0000<![CDATA[New comment by chikinpotpi in "1B identity records exposed in ID verification data leak"]]>Nobody told their marketing department:

https://www.idmerit.com/blog/idmerits-data-breach-fail-safe-...

archived for posterity: https://archive.ph/MdSfO

]]>Thu, 12 Mar 2026 13:39:36 +0000https://news.ycombinator.com/item?id=47350395chikinpotpihttps://news.ycombinator.com/item?id=47350395https://news.ycombinator.com/item?id=47350395<![CDATA[New comment by chikinpotpi in "There Will Come Soft Rains (1950) [pdf]"]]>how dare you make my feel my own feelings

]]>Thu, 05 Feb 2026 19:41:51 +0000https://news.ycombinator.com/item?id=46904075chikinpotpihttps://news.ycombinator.com/item?id=46904075https://news.ycombinator.com/item?id=46904075<![CDATA[New comment by chikinpotpi in "That boolean should probably be something else"]]>I generally prefer to let one value mean one thing.

Allowing the presence of a dateTime (UserVerificationDate for example) to have a meaning in addition to its raw value seems safe and clean. But over time in any system these double meanings pile up and lose their context.

Having two fields (i.e. UserHasVerified, UserVerificationDate) doesn't waste THAT much more space, and leaves no room for interpretation.

]]>Thu, 28 Aug 2025 13:37:06 +0000https://news.ycombinator.com/item?id=45052002chikinpotpihttps://news.ycombinator.com/item?id=45052002https://news.ycombinator.com/item?id=45052002<![CDATA[New comment by chikinpotpi in "Amazon Aurora DSQL"]]>So... its like cockroach db but with the added feature of more vendor lock in?

]]>Tue, 03 Dec 2024 18:19:29 +0000https://news.ycombinator.com/item?id=42309332chikinpotpihttps://news.ycombinator.com/item?id=42309332https://news.ycombinator.com/item?id=42309332