You can download the entirety of wikipedia and store it in your own offline immutable backup.

The dump of english wikipedia is 26gb compressed and completely usable with that compressed format plus a small index file.

That's small enough to live on most people's phones. It's small enough to be a single BluRay. Maybe Wikipedia should fund some mass printings.

What you do not get however is any media. No sounds, images, videos, drawings, examples, 3D artifacts, etc etc etc. This is a huge loss on many many many topics.

I recently had a performance review at a FAANG. One engineer on my team has spent the past 3 years working on a complex infrastructure migration which involved about 20 engineers. The migration was completed last year and saved the company some opex costs.

I on the other hand spent 3 weeks optimizing our core service and reduced 2x the opex costs of the large complex 3 year migration.

In my yearly review my manager acknowledged my impact, but said I need to solve more complex problems to get to Staff Engineer. I protested saying that my 3 weeks of work had a larger impact than 20 engineers over 3 years, but he told me that is just how it works.

Modern AMD processors are basically a bunch of smaller processors (chiplets) glued together with an interconnect. So yes single chip nodes can have many numa zones.

That was Zen 1, the later ones don't have per chiplet memory controllers, it's all on the single IO die, and they are not NUMA for a single socket.

BGP based routing is a major pain in the ass to do on-prem. If you want true HA in the datacenter you are going to need to utilize BGP.

I mean, BGP EVPN is the datacenter standard. (Linux infra / k8s / networking guy)

There are standards but actually designing a sane network architecture, buying all of the correct network hardware, and configuring all of the software to properly use that hardware is hard. At my company we have a team of about 20 people whose job it is to just design, install, and run the network.

> There are standards but actually designing a sane network architecture, buying all of the correct network hardware, and configuring all of the software to properly use that hardware is hard. At my company we have a team of about 20 people whose job it is to just design, install, and run the network.

Network engineers do network engineering :)

Work/school days should just be shorter in the winter. We can easily leave work/school an hour earlier in the winter and nothing bad would happen.

My local BC school district does not have winter hours, it is the same all year.

You are not alone according to polling in BC.

I think fundamentally it comes down to energy for me. I have very little energy in the morning so I am not going to harness the pre-work daylight hours to do something outside like taking my dog to the park, biking, or running. For me I don’t actually start feeling energized until maybe 9-10AM.

After work however, I have much more energy to do things outside with the daylight.

100%. Almost nobody goes to bed at 8pm and wakes up at 4am, so high noon is a pointless exercise.

Penticton is also in a valley so in reality the sun goes behind the mountains in the west around 3:30PM.

Winter sucks anyways when you live in the north. I grew up at 56 degrees north and you are cooked no matter what is done. Better to optimize April-October.

In summer when there's lots of sunlight, the benefit of an extra hour--while not zero--isn't that significant.

We tried permanent DST in the US in the 1970s. People hated it.