It seems like they are re-implementing a half baked OTP lookalike, but they aren’t actually using Erlang/OTP under the hood which gives me pause as the Erlang/OTP implementation has been battle tested over many decades now whereas the gleem implementation is a complete rewrite.

In my experience the most effective work pattern for me is using agents to perform research and feedback on high level design, then I write the code manually, then I ask the agent to review the code for potential bugs/issues and fix those. The agents have a much easier time making small changes once the design is 90% there without going fully off the rails and generating slop.

I am working on writing skills to make the agent better but it is a bit painstaking. For example I had to write this inside of a skill because sometimes the agent would just stub out methods and leave TODOs: “always fully complete the requested task before finishing edits unless input is needed”.

I was a terrible student until high school — where I could start entering into college classes and/or skip classes — because the pace was too slow and I got bored and caused issues. Having the opportunity to do advanced classes was a huge gift for me and my peers I no longer disrupted.

Other orgs have never heard of alerts or error reporting and naturally will not catch issues until they are catastrophic (for example services that crash frequently in the background go unnoticed until the crash frequency causes a catastrophic failure). In my experience a lot of issues are pretty simple such as running out of memory, CPU throttling, crashes caused by simple bugs (nil panics). If you have good observability you can catch those issues early.

For example: people rag on Ceph that their cluster somehow got into a broken state, but that really only occurs when abuse of the ceph cluster has went on long enough that the cluster finally reaches the tipping point where it is unrecoverable. If you set ceph up, follow the correct replication rules so components are spread across failure domains, and use the metrics and alerts that are distributed with ceph it is actually quite hard to break the cluster.

Sure, but you actually have to work for continued income. Wealth accumulates with no input once established.

Wealth has the ability to increase (capital gains) without having to pay tax until it changes hands, whereas when income increases it is immediately taxed at a higher rate. Additionally, wealthy people can use securities as collateral for near zero interest lifetime loans which also bypass having to pay income tax.

Also, I bought a rav4 hybrid which is one of the most common cars on the road here and therefore mechanics have a lot of experience working on these vehicles.

The real question is why github has 3800 internal repos.

Hashing passwords has been a thing for at least 50 years now. V3 unix had /etc/passwd which hashed all user passwords. Notably, these hashed passwords in early unix have been cracked: https://arstechnica.com/information-technology/2019/10/forum...

I guess you got your answer.

Why is that? You would think the company ending events like IAM going poof due to it being dependent on us-east-1 would be top priority to fix?