rllin's comments

"One weird trick" is still pretty much the first way to go for most recommendation systems that are large embeddings focused. see torchrec, nvidia's hugectr

really you should treat your entire cloud deployment (sans state where impossible) as cattle

did nobody read the article lol

> The organisers say the sequence is often picked. But some have alleged a scam and an investigation is under way.

> It is extremely rare for multiple winners to share the jackpot.

that sequence happens, but multiple winners is rare

so the combination of them is the concern here

yep demand side subsidies do not have good outcomes

supply side are a bit better

wrt cost disease

see how milk has remained the same price for decades

spiritual successor

AGNB needs some time to grow into longer format

they're literally 3 dudes in an RV without a working toilet

if they had BBC money they would live up to Theroux 100%

you only need two operators, the kubeoperator, the dataflow operator

and then every task is just a standalone, vertically scalable service on k8s or a giant horizontally scalable compute job

the thing is humans have most efficiently encoded (in detail) reality in text. humans already highlight what is worth encoding about reality.

for example, you can finetune gpt-2 to have an idea of sexual biology by having it read erotica. just like how you can have a model learn the same by watching porn. but it is much more efficient to read the text, since there is much less information that is "useless"

AGNB is the spiritual successor to Louis Theroux

it's what Vice tried to capture but failed. parachute journalism works, only if you inject very little of yourself into it and have minimal framework.

anybody know if 5g is worth waiting for?

lol it is so rare for a company that goes belly up to hurt someone's career

it's a specialized swab shortage

It really looks more and more like JAX is the internal winner after the tf 2.0 fiasco

not op...

google deployment manager. it has incredibly subpar support for other GCP services. all support interactions resort to them suggesting migration to Terraform. we do use it in production, but not without great headache.

this isn't an explicit kill-off, but certainly purposefully offering bad support

this is in a class of problems i've been thinking about recently

- usury

- patents

- copyrights

- land

- software as a service

the first 3 all have some slowly changing socially acceptable period of profit. and they are all enshrined in law. but this means there are also frameworks in place for adjusting this period of profit (lobbying, etc.)

the 4th is only capped by property taxes and sometimes with unintended consequences (cf. prop 13)

the 5th is unregulated and seems socially acceptable to have no definite end date due to a combination of (sometimes artificial) technical difficulty (need for support, e.g. RedHat, any other company based on FOSS) and slow addition of pithy features.

i'm not sure i have any conclusions, but I think this framework is useful because it allows us to examine it with an older moral framework rather than a more (post) modern marxist.

not only does the industry not have a labor union, there's a culture of passion which is almost like having a negative union.

any time passion is involved, you are being paid less than market. cash is a more liquid currency and can in fact buy passion.

Responding in general to the meme of "but what is your time worth?"

people often underestimate their ability to change their own utility functions. If you're watching 4 hours of TV every night (or reading or w/e other "mental recharge" activity) simply change your utility function to let financial planning "recharge you."

The ultimate arb is changing your own utility function.

Obviously this may be harder or easier for some people, but it's a very learnable skill.

frustratingly slow for word docs. antiword is better for those of you who wish to convert word docs en masse

a bit ignorant in this area, but how is this functionally different than Google Cloud IAP?

we use this in production (flags for kube execs of python scripts)

it is bounds better than argparse and click. would highly recommend.

important to note here, that a lot of this is thanks to the python team's continued extension of the inspect module.