heleninboodler
Joined 7 years ago
Joined 7 years ago
I personally have taken both paths, and made what I considered a ridiculous amount of money at a startup (after I'd been gone for a while, having bought my stock). When I got my cash out, I didn't quit my not-technically-FAANG-but-pretty-close job and that comp continues to grow. I never expected this, but my comp has grown to the point where the cumulative amount I've made here has actually surpassed the startup money. 7 years at each place, and the steady paycheck eventually outpaced the big windfall. The difference is I can keep the steady paycheck indefinitely, so it's definitely the win if I stick it out. Of course, now I'm itching to do a startup again. :)
For me, it has nothing to do with the price and everything to do with the fact that I don't want a service dependency for my most critical passwords. I want them to be available no matter what. The product should be standalone. And this isn't a hypothetical concern, either: my employer is contractually mandated to disallow cloud-based password managers, so I must use standalone ones (yes, this is a stupid policy, but one that I'm bound by).
And on top of that, 1Password 5 was an excellent product and it is just steadily getting worse, in my opinion.
I think that's just what the cylindrical room is often called when it's used for motorcycles. The paper repeatedly references it, abbreviated "WoD." I don't think there's any death involved. :)
I don't think this really has much to do with the "infinite" nature of the canvas. Individual instances of infinite canvases have a finite size. :)
Also, this is not very json-ish, but optimizing your serializer so your metadata is always written first is pretty handy for embedding, since it allows you to use a pull parser and do useful things before the entire doc is parsed. (e.g. picture a huge doc being embedded and starting out as just a box and having its elements filled in async. You can't do that well if you don't know the bounding box ahead of time)