dangoodmanUT

If they're referring to the recent tumble, I wouldn't suggest anthropic incited that

coreweave did

i'm sure ant didn't help, but thanks for the fire sale i guess

it's not obscurity if they don't have the key, it's encrypted (yes i know quantum computers)

It's more secure to let a cloud push immediate patches than to self host in most cases (cloudflare has always been good about this, e.g. php and log4j)

the problem is owning hardware is hard

A trick i've started doing is encrypting my env vars, then hard-code the decryption key in the code

that way if the provider gets popped, they need my binary to decrypt it

it shouldn't be necessary and it sounds stupid, but in cases like this, it proves invaluable (it appears they don't have customer code/binary access, but maybe that wasn't important enough to mention)

Unfortunately for infra startups, I think we're going to see a convergence back to hyperscalers as a result of incidents like this and railway.

There's no amount of "nicer to use" that can replace security, at least certainly when selling to enterprises

"tk is gonna be pissed" you hear echoing in an SF bluebottle

One of the many reasons i preferred mac is because they never tried to force touchscreens on to people

ive never seen someone use a laptop touch screen effectively

just get an ipad

I attribute this to "it's so new and we don't know what the right answer is yet", but you may very well be right

It's nice to see JetBrains finally wake up and realize they can't sell a Cursor competitor from 2024 anymore. Something about JetBrains writing a new IDE seems bold... not sure if it feels correct.

Some of these are objectively bad: buttons should not resize for spinners, etc. otherwise the whole website layout can shift

but the animations are nice

so i see we're still going with the apocalypse today too

imo if you're going to run k8s, have it hosted

same as a db, better to pay #x as much and have it hosted then to be wishing it was not your problem when it was down

and we may very well live in different versions of the world. i'm on the frontlines of startups so we move with the customer, rather than making customers move with us

its not reading, its observation. see other comment abt spiky-friendly workloads

schedulers that can handle spikier workloads generally

believe me i love k8s, and i think agents wield it amazingly well, no more yaml-slop or kubectl (`k`) slop, just yell at claude to fix it