HN user

dclusin

1,288 karma
Posts6
Comments483
View on HN

I recently bought age restricted materials online and had to upload a picture of my photo id with a selfie to a 3rd party verifier. Similar to what crypto currency verification goes through.

I think the underlying disagreement/debate is whether or not these initiatives are in good faith. Any implementation of this is going to be imperfect and a motivated person will probably be able to get around this. So the debate, I think, is, if we implement this are we going to incrementally improve it? Or is it just a pretext to point to and say, hey look, this can never work perfectly, so we should ban x, y, and z.

Assuming you’re pretty close to the hardware? As a standard backend web service dev os/library/device bugs are incredibly unlikely and usually defective application software is to blame. Not saying it doesn’t happen, but I can’t recall in recent memory this sort of thing happening as high up in the stack I work.

In addition to this I think picking problems that you don’t immediately know how to solve but is within your wheel house is important. Also sticking with a single problem or domain. Constantly starting and never completing things doesn’t expose you to the next iteration of challenges.

They haven’t included an amortized cost breakdown with depreciation of hardware including backup. Or the geographically local personnel required (data center remote hands or dedicated employee that gets the call?). Even still I suspect it’s still probably cheaper.

Also it looks like these are retail prices. You can get cost savings by negotiating but I’m sure there’s an NDA required.

Definitely had this happen in recent memory. Also the thing to be careful about here from experience is you still need to qa the contractors deliverables. Team had a contractor delivering features and it turns out what was “delivered” many times didn’t actually work. Wasted several months of my engineering time babysitting and validating said contractor. Net result was wasted time and money as we just ended up reimplementing ourselves.

Almost half the screen real estate on my iPhone SE was white space. I had zero interest in reading something, especially something that long and in depth on a page that wastes so much space for literally nothing.

Typography, layout, and presentation counts for more than coders such as myself will ever admit publicly :)

Market cap of pre-acquisition twitter is why the company is drowning in so much debt. Had he timed his acquisition better perhaps it would have been more sustainable. Its market value collapsed a few months after he made his acquisition offer. Ergo less debt.

Your suggestion at the end assumes he can predict the future wrt to the collapse of twitters market cap at the time he made the acquisition offer. The reality is he made a binding decision that he was stuck with that looks terrible in hindsight.

I do agree that he could have handled the situation a lot better. But some things are outside his control.