Happened to me with coinbase, I accidentally subscribed and got charged for 3 months. Luckily they were able to refund me since I didn’t actually use the service.
271 karma · joined March 18, 2019
Happened to me with coinbase, I accidentally subscribed and got charged for 3 months. Luckily they were able to refund me since I didn’t actually use the service.
The source of truth would still be the code though, otherwise the declarative statements would get so verbose that they wouldn't be any more useful than writing the code itself.
I get that a lot of indie businesses probably don’t have the resources/want to do this, so there are solutions you can buy, but they’re expensive and mostly targeted at high volume merchants anyway. Maybe stripe launches a fine-tunable radar product someday?
All else equal I think a longer term success is more admirable, but many companies end up existing primarily to keep themselves alive. They acquire startups and ride out brand well beyond their useful life. At what point do these companies become net harmful?
- wood sticks to clean off the watch without scratching
- bright green mat for high contrast against small parts
- soft cushion pad made it easier to pick up parts on a flat surface
- the ring around the replacement main spring to make it easier to press into the barrel
(idk anything about watch servicing, just my guesses from watching the video)
(self plug) I'm also working on an NFT parody game https://apps.apple.com/us/app/id1609874752 - it's a simulated trading & collecting market for emojis.
I'm always confused why people call cryptokitties a game, there's barely anything to play with. Maybe using blockchain makes it a lot harder to implement actual game features, or maybe it just corrupts your incentives lol.
https://www.amazon.com/Crayola-03-9000-Crayon-Maker/dp/B0029...
I started developing with UIKit for a year, hated it, then switched to SwiftUI and have built multiple apps over the past few years. IMO the "last 10%" bugs are not that big of a detractor compared to the benefits. Of course some of this is my bias; I'm more likely to spend time trying Stack Overflow hacks on SwiftUI bugs when the UIKit solution is better. I have to "work with the grain" sometimes if something just isn't possible in SwiftUI, but I'm fine making that tradeoff. I feel lucky not having the bias of years of UIKit, it's hard to let go of something when you're so used to it. I'm also lucky to not be working on apps with backwards compatibility issues, but I do think SwiftUI is the way to go for new consumer startups.