• 2 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: June 1st, 2023

help-circle












  • Good article for discussion.

    Health checks is one situation where kubernetes really shines. It makes a clear distinction between readiness probes (when the pod is ready to start serving traffic), liveness probes (when the pod should be considered dead), and startup probes (when the pod has finished bootstrapping). Coupled with autoscaling it then becomes acceptable to have a pod stop serving new traffic when it’s too busy, because other pods can be created in a short time to take the extra load.

    Including backend checks in your application depends on its nature. I think the mistake that the article’s author made was not to include the checks, but to have too big of a blast radius when the check fails.


  • The rationale for using LTS distros is being eroded by widespread adoption of containers and approaches like flatpak and nix. Applications and services are becoming less dependent on any single distro and instead just require a skeleton core system that is easier to keep up to date. Coupled with the increased cost needed to maintain security backports we are getting to a point where it’s less risky for companies to use bleeding edge over stable.



  • Both are concerning, but as a former academic to me neither of them are as insidious as the harm that LLMs are already doing to training data. A lot of corpora depend on collecting public online data to construct data sets for research, and the assumption is that it’s largely human-generated. This balance is about to shift, and it’s going to cause significant damage to future research. Even if everyone agreed to make a change right now, the well is already poisoned. We’re talking the equivalent of the burning of Alexandria for linguistics research.