thelastknowngod

There's no one answer here. It's going to take a lot of trial and error and experimenting. All of the issues you mention are going to have to be addressed individually as well. There is never going to be a single tool to do this for you.

As far as tracking state over time, standing up a proper, modern monitoring stack will help tremendously. If you send logs to loki, collect metrics with Prometheus or OpenTelemetry, and graph them both with grafana, you should have really great insights to whatever is happening.. It's never going to be finished though. It's always a work in progress.

"Giving a single government agency the power to arbitrarily set the price of medicines with little accountability, oversight or input from patients and their doctors will have significant negative consequences long after this administration is gone," Pharmaceutical Research and Manufacturers of America (PhRMA) President Stephen J. Ubl said in a statement.

Oh.. I can see it now. Patients and their doctors begging for more expensive drugs.. The government saying, "Yeah! These fucking people aren't paying enough! Let's negotiate with the drug companies for HIGHER prices! That will get us reelected!"

Get fucked, Stephen J. Ubl, president of Pharmaceutical Research and Manufacturers of America.

Watercolor.

Children play with $5 palettes. Apparently I pay $20 for a single color tube.

Knowing this stuff is fine but make sure to keep your goals in mind. If the idea is to get a job, figuring out how Bluetooth works isn't going to get you anywhere. You need to move in the direction the wider industry is moving. That direction is running containers in kubernetes.

If you can stand up a kube cluster, write a Prometheus exporter in go, scale pods based on those metrics, and auto resize workloads' resource requests, then you should be able to find a job without much trouble.. These are the things ops people are expected to do in 2023.

EDIT: The CNCF is a great resource for modern tooling.

Yeah interesting idea. I can see it being useful for private enterprise implementations of gitlab to contribute to upstream projects.. I don't think it's possible to fork a public github.com repo to a self hosted github enterprise instance but it's been a while since I've run that and I don't remember ever actually trying.

It might make tooling easier.. I can see it being pretty easy to setup bi-directional comms with non-gitlab CI/CD pipelines doing this.

Really it might entirely eliminate the need for service accounts or whatever the gitlab equivalent of Github Apps is too which would be wonderful.

I still get nagged constantly to add a birthday to my Google account to make sure I am older than 13 or something.. To satisfy some dumb law I think. The email account is like 15 years old though. How could I be under 13 if it's that old?