longcommonname

Most developers just want to work on tickets other non infra related tasks.

For the majority of those contributors its really helpful to give them a happy path. This happy path also makes supporting much easier.

This happy path comes out as a platform and series of tools on top of the k8s layer.

I love working on infra automation, and I love enabling other teams. When I did nothing but dev work the feedback loop for when I helped someone could be months. As an SRE I help dozens of people every week with near real-time feedback.

Im an SRE. I started off my career as a dev.

I write code, yaml, hcl every day.

You sound incredibly bitter.

From a max of 200 MB/s. To max of 1MB/s for each index.

Or you can signify the context using shell prompt and use kube rbac to give read only permissions instead of letting people mess with your prod cluster.

Rewrote a logging framework that logged petabytes per day.

Gcp terraform linting is sorely needed,.

I wonder how they will handle their supply chain difficulties. It looks like they are releasing this in fall.

I currently have an order pending for 50 days still waiting on inventory to arrive. Their communication on this has been incredibly poor and definitely not what I expect from Lego.

I look forward to the air fare article. I worked at 1G for a few years and am interested in seeing your take.

Push based monitoring has its own flaws. Mainly service discovery is coupled with service health.

Pull based monitoring makes it so you can remove the service and independently recognize failures.

If your plane isn't full enough you lose money. You want to be able to predict when to cancel flights early enough you don't have to refund too many customers without wasting money on empty routes.

You also need to manage how much you're overbooked to allow for full flights when people miss their flights or cancel at the last minute.

You also need customer support for all sorts of actions.

These are just a few of the many hard problems they face.

I switched to ChemE after ochem. The memorization sucked and much preferred the math in courses like pchem and thermo.

Rash decisions like this aren't going to do anything but hurt the students.

This is incorrect, we would ask "have you had sex with a man who has had sex with another man in the last 12 months". This got around the case you dealt with.

This is incorrect, we would ask "have you had sex with a man who has had sex with another man in the last 12 months". This got around the case you dealt with.

For public health and public trust of the blood supply there's a 12 month deferral to donate after a male has sex with another male.

After you come in contact with a covid infected individual, for public health there's a 14 day quarantine.

No testing is perfect, false negatives could lead to disease transmission.

Think about things that have increase in values during during a clearing period. Stock dividends is one.

I remote work because I don't want to commute.

I worked at a GDS and you're pretty close. There's a component of not wanting to change, but when they do they are burdened by their fragile infrastructure and thousands of competing projects. Very small changes would cause defects in one project that one customer uses. While massive bugs are ignored.

Often I've had to ask specifically for positive and constructive criticism. Many times managers are afraid of providing negative feedback.

Younger invesres and not just men are migrating from traditional blue chip stocks that their parents prefered.

Really the most difficult part is mirroring everything, but managing your dependencies without using the latest tag

Short build times come with less compile time checking.

You can get cpp programs down to seconds for incremental builds with good management while having compile time checking.

18 out of 300 to 400

I refuse take home tests, we need better ways of triaging talent not better ways of wasting my time.

I love this type of work, the final analysis shows a significant change but one that I've had difficulty with in the past. Decrease your variance and your 99 percentile and your going to see gains even if you see an increase in your volume of times near the median.

So often we see projects that talk about cutting costs by order of magnitudes but this one is taking an order of magnitude of pods greater than most of what we will do and reducing it fractionally

Don't give everybody prod access, but give enough people prod access.

Use namespaces and logically bounded clusters. Get your monitoring, and tracing and a dashboard to visualize this figured out now.

Canceling a talk doesn't equate to changing a view.

Theres still locations here that can't get fiber. The local hospital is owned by a church and they own apartments adjacent to the hospital. These apartments are surrounded by others that get fiber but the map still shows they aren't planned.

Most infrastructure folks love to talk about the expensive costs that occur from incidents like fires, the lazy infra engineers who don't do anything, hurricane shut down my data center, etc.

Devs like to focus on costs related to lost time. This is a pretty common trend and not really sure why you think that there's anything pathological about k8s. Maybe there's something pathological about infra folks in general and dev folks.

And their own serialization format