transect

I agree. Though I will say that IAP and gsuite groups backed IAM is nice.

My favorite mysterious light sources is a triplet off the coast of Newfoundland: https://www.lightpollutionmap.info/#zoom=6&lat=5798060&lon=-...

I assume it's some sort of offshore rig.

In my truck I can lock all of my windows to keep kids from rolling them down. If I'm driving alone I can roll down the passenger window without leaning over the bench. My windows have a behavior where the window will roll all the way down automatically if I press the button with a certain duration.

All of these features mean I almost never think about the state of the windows while I'm driving for more than a split second. I think that's a safety win.

Also it's just nice not to have to roll down a window or rewind a vhs. Micro-comforts add up.

We use Jenkins to invoke Tekton pipelines (https://github.com/tektoncd/pipeline) with a wrapper we wrote. The pipeline runs, outputs junit to a bucket and we pull it back and give it to jenkins. Was a bit of a lift to get working out of the gate but it's been mostly smooth (and flexible and cheap) since then.

We use preemptibles for our CI fleet and it's great. We can run a hundred instances at full tilt boogie for 8 hours a day and the nodepool downscales to zero while we sleep. It's a no brainer if your controller (and use case) can handle preemption gracefully.

For citation here are two sources:

50% of population: https://ourworldindata.org/urbanization#how-urban-is-the-wor...

70% of emissions: https://www.c40.org/why_cities

This is based on the concept of a "consumption emission", which is an interesting concept. The point being that cities (especially western cities) have seen their emissions drop due to de-industrialization, but consumption has increased (hence your statement about carbon footprints correlating to wealth/income). To say that cities impacts are smaller when they just outsource all of their carbon impact is disingenuous.

> Further, the definition of "city" can include a lot of sprawl in places like Houston, Phoenix, and even Beijing and Tokyo.

Is it the case that you get to cherry pick which urban center is a real city based on how green it is?

I used to go to NYU medical, which uses Epic. As janky as their interface is, it was nice enough to use and see all my charts, etc, as well as communicate with doctors over email. So when I moved to another city I specifically chose a medical system that used Epic. Once I got my login I then logged into my NYU Epic to initiate a data transfer and wouldn't you know it... it was impossible. After digging around to no avail I contacted my new provider and they told me the best thing to do is print out a PDF of my medical history in NYU's Epic and they would scan it back into their Epic... with a complete loss in structured historical data (bloodwork, vitals etc). Insane.

Here's the reddit thread in question:

https://www.reddit.com/r/rust/comments/epoloy/ive_smoketeste...

I have no doubt it led to some github issue brigading, but it's not really that big of a deal. Ostracizing /r/rust in a mealy mouthed way probably won't make that community better...

For CI (testing) we use tekton [1] to run tests and pass around artifacts inside k8s. You can kick off and monitor tekton builds with their CLI tool, but we ended up building our own create/monitor/download-artifacts tool for it in ruby. We use an off the shelf CI server to kick that tool off, and it dumps back results the CI server can understand.

One of the things we need to do is elastically scale the number of tasks (basically pods in tekton) that comprise our test suite run. This might be based on cluster utilization or whether it's the master branch. Since we have a single threaded test suite, we hoist parallelism up to the k8s level by breaking apart the tests into partitions each run by its own pod. For this we just render processed and parameterized erb to yaml. Eventually we'll dispense with yaml altogether and programmatically construct resources using a k8s REST api client.

We haven't moved into CD with any of this tooling yet.

[1] https://github.com/tektoncd/pipeline