My second closest childhood friend died from leukemia about ~18 years ago, when we were about ~10 years old. I still think about him sometimes and even now as I'm writing this I feel some sadness.
According to my mother his mother was head nurse of pediatrics and had not noticed my friend becoming sick, and he became very sick.
He was given kemo therapy and subsequent bone marrow transplant, but he didn't get better.
Apparently the kemo made him blind and more afraid until his death.
And his death took a toll on his family, and especially his twin sister, which their mother lashed out at and was told by their mother that "she should have been the one dead."
Childhood cancer ruins so many people and relationships, and I deeply hate this thing that almost seem intrinsic to the human condition.
This looks inspired by the work Snowflake did with their now FOSS Polaris[1]. Great to see more innovation in the space.
I had a quick look through the documentation[2], and it looks like it's not API compatible with the Apache Iceberg REST Catalog spec, which is somewhat dissapointing.
Why do companies more or less openly discriminate against older people?? It's nice to be able to have a more experienced professional give advice and help you out.
I've heard multiple times when interviewing for jobs, that their company has a "young" culture and it always made me uneasy.
During my 3 years as a backend developer at my current job I've seen a lot of application of "serverless" stuff from AWS, and I've also used quite a lot of those services myself.
Personally I would never use something like Lambda for compute, unless it's something that needs to integrate between another AWS service and something else (likely also a service.)
Also it seems like the "serverless" hype started (atleast at my employer), because some higher ups didn't trust the developers in my department, when they first had an AWS account provisioned.
My general feeling about picking the right tool to solve a problem is to, firstly, pick the problem apart. Then you can evaluate technologies that can solve your problem. This includes code that you already own and it should most likely be this one that you pick. After that you can start to look at other technologies to bring in.
Arguably it's nice that with AWS you can spin something up relatively quickly, however sometimes I'm also stumped by their limitations and what workarounds that seems to pop up as a result of that.
I'm not affiliated with any of these names, I'm just really interested in IVM:
Materialize Readyset Feldera RisingWave