392 karma · joined December 10, 2016
Nowadays, depending on the project’s complexity I either run just 1 sprite, several sprites, or in one case 1 permanent “CTO” VM (with a dedicated GH App identity) that specs work that a fleet of worker sprites pull and implement.
(black goes first, white has Komi, so really a 260+komi points lead)
edit: another key addition by NextDNS is a global infra footprint, rather than just in the EU. Oh it looks like there’s no anycast with the non-profit as well? And you have to pick your local resolver. I guess that makes sense because the main value prop of NextDNS (to me) is when I’m traveling and a local pi-hole won’t suffice.
Comment from `amanchanda`, i.e. the OP.
Nice hustle writing an Ask HN post to then plug your own product, but you have to make sure to respond to questions with your _other_ account `nicooo`. ;)
Good news, you now have time to pick up The Bazaar instead! (joke aside, it's quite fun, a lot more chill, and not nearly as exploitative as Hearthstone)
Maybe they want to place a temporary charge to verify the card's valid? I don't believe you can do so with a debit card.
See drand, the distributed randomness beacon protocol at https://drand.love/
There's something unique about deeply technical products, and startups founded by engineers, that often lead them to similar challenges. There's also a unique requirement that engineers must shape the product at least as much as PMs, however technical they might be. While there's no silver bullet in my doc, there's some opinionated advice to avoid common pitfalls at various stages.
I'm not looking for new customers; I just figured that some technical founders or PMs out there might find the doc useful while navigating their own 0-to-1 journey. Cheers!
Peak 2020: https://www.wiz.io/blog/wiz-comes-out-of-stealth-with-100m-s...