I can, I’ve written a billing system before (unfortunately). There’s a lot of annoying math/edge cases and systems to sync between.
While I never implemented a restriction like this, it would have prevented a lot of weird bugs/customer support issues and kept the underlying code much simpler.
(Annoying math = time zones, prorations, discounts, billing cycle anchors, etc. see the “falsehoods programmers believe about X” series)
(Systems to sync between = internal DBs, billing APIs, payment processors, etc.)
I mean sure, I get it, but companies like Uber leave edge cases like that out when it hurts them (customers cancelling) but move heaven & earth to remove them when it helps them (I bet its easy to re-join within 24 hours of cancelling?).
My experience from working in the security space is that all the tech is pretty un-sexy (with very good sales pitches), and none of it will save you from a nation-state attacker.
The NSA's capabilities back in 2008 were pretty astonishing: "RAGEMASTER" A $30 device that taps a VGA cable and transmits the contents of your screen to the NSA van sitting outside! Crazy stuff. Makes you wonder what they've built in the last 15 years.
What gives you confidence that this is a bot account and not a frequent reader of HN that is passionate about growing the number of unique topics discussed here? And what’s up with the strong, inflammatory language?
Designing fonts for languages that use Chinese characters is often challenging due to the sheer number of glyphs.
This approach to generating fonts is very interesting… feels like it could unlock the creation of heavily stylized fonts that just wouldn’t be feasible otherwise.
I don't think so. The metaverse is the obvious endgame for entertainment. The only question is how long it takes to get there. Zero marginal cost everything is just a continuation of what made software so succesful so I think it should be clear to HN users why the idea behind the metaverse is so powerful.
While I never implemented a restriction like this, it would have prevented a lot of weird bugs/customer support issues and kept the underlying code much simpler.
(Annoying math = time zones, prorations, discounts, billing cycle anchors, etc. see the “falsehoods programmers believe about X” series)
(Systems to sync between = internal DBs, billing APIs, payment processors, etc.)
reply