rawnlq

The author is obsessed with fitting things with a logistic function and drawing wild conclusions even when it directly contradicts itself.

You can't have the rate of publication be a logistic function and the cumulative publication be a logistic function. The derivative(i.e., rate) of the logistic function should be 0 at both tails which isn't S-shaped anymore.

All your bits will rot if your house burns down. You will need something cross region (maybe your whole city gets nuked) but then you'll be exposed to the internet again. Snail mail your drives I guess?

Making the company money is the not the only factor is it? Any engineer at google/facebook/etc are probabilistically making the company multiple millions per year too (terrible estimate from revenue divided by headcount). But probably only a handful of them would ever be able to demand the rate you charge because they are replaceable.

How do you make sure the company won't just take your advice and hire a guy to do this for 90k/yr instead of letting you work on it for three weeks?

A more layman version:

- Each value generates a sequence of coin flips

- Count the number of consecutive heads until you hit your first tail

- Take the longest streak amongst all your values, call it n

- Report 2^n as your estimate

This works because if you only have a few people flipping, you won't get a lot of long streaks.

But if you had lets say 1024 flippers, you expect to see one person flip 10 consecutive heads.

Coins flips here are just the bits generated by hashing the value so each coin flip sequence will be the same for each value.

I forgot where I heard this from but I thought the reason reddit didn't monetize well was because the users were either using adblock or were too tech savvy to click on ads?

I have been using reddit for probably a decade now but don't remember ever clicking an ad. OTOH I typically misclick on a few links before I get my download when visiting pirate sites even with adblock on.

Was totally expecting this to be a plug for firebase (google's realtime database) but it actually comes with a koa server using websockets. Seems to be built with redux under the hood. No fancy conflict resolution and does syncing by serializing entire app state and sending it to each client after each move.