di456

> At least this firmly puts to rest the myth that taxes are somehow proportional to the government services you use.

You are confusing "service fees" with taxes. There are various tax regimes. Very few of them are proportional to the services you use.

Prior to the 2016 US election I heard with complete denial that the presidency is a reflection of the sum of our culture.

I was wrong.

This makes me wonder, what if there's actually a narcissism crisis disguised as a mental health crisis?

> So we are probably just one of the first.

We don't really have any way to know that. Considering that there may be as many stars in the sky as grains of sand on Earth, there are many many unknowns.

For another example we don't know for sure if our universe is the only one and it's entirely possible that everything that could ever happen plays out in real time across and infinite number of universes. We don't have any way to physically measure that possibility yet. We only have mathematical theories.

Similar to how Copernicus proposed the heliocentric model, maybe our universe is not even the center of existence?

It is humbling to imagine.

40mg is a huge dose, no?

The base proportion to the height.

Two bricks wide has a 2x wider base.

With python I'd decompose that one-liner into several variables for readability. That probably ends up using more memory than it would otherwise but I generally don't work on systems where that matters much.

Scala was really nice for this syntax when I used it for Spark.

I'll second this too. As a former manager told me, figure out how to scale yourself. Making the end to end development lifestyle easy for peers and partner teams is one way to do that. It could just as easily be called platform or systems engineering with a touch of DevOps.

It's like UX for data people. How to make a cohesive experience among the various tools, scripts, services that people use day-to-day so they can use and maintain datasets efficiently.

Sounds like you are on the right track.

A non-technical benefit is there won't be so much context to keep in your head when triaging data issues in the future.

A database table is very similar to the separation of concerns problem of core software engineering. A table really just is an abstraction for storing and fetching various data points.

Finding the right balance is part art and part science.

It is important, but when the shift to cheap compute and storage hit an inflection point it became possible to build out wide tables that combine the characteristics of facts and dimensions, and real data modeling took a back seat. That possibility led to bias toward moving quickly with less emphasis on making the data model sustainable.

I'm seeing the pendulum start to swing the other way, where the complexity of these scrappy and loosely structured data models is hampering the ability to innovate, and even slowing down the business. The models are often inflexible and hard to maintain with hidden bugs and gotchas.

Just don't tie yourself together by rope while on mountains. One goes down, everyone goes down.

Deep Survival is a great read. I picked that up from it.

Human infants will die without physical touch. We are social creatures by our DNA.

The worst punishment in older times was banishment. It was usually a death sentence.

No, that's crypto. And some parts of AI.