> Looking over this PR, the vast majority of the code is a DWARF library by itself. This should really not live in the compiler, nor should it become a maintenance burden for the core devs.

I think this is a good point, that publishing a library (when possible, not sure if it's possible in this case) or module both reduces/removes the maintenance burden and makes it feel like more of an opt-in.

> Metaprogramming style in C++20 only has a loose relationship to previous versions. It is now concise and highly maintainable. You can do metaprogramming in the old painful and verbose way and it will work but you can largely dispense with that.

This was my takeaway as well when I revisited it a few years ago. It's a very different, and IMO vastly improved, language compared to when I first used it decades ago.

> To my knowledge rather consulting firms are great at selling the necessity of lots of consultants consultant days: Just let the customer talk very openly about their wishes for the project, and you immediately get an insane scope explosion for the project, i.e. it "needs" an insane amount of consultants over many years to implement all these wishes.

"Oh yeah, we can do that!" Boom, there's a team...somewhere...working on it. It's a line on an on-site project manager's status report.

> For final grading I saw the excavator trucking out what looked like native soil and trucking in rocky soil.

They sell the topsoil and replace it with cheap (rocky) fill. Every. Time.

Yes. I started taking medication, which helped pretty much everywhere in my life.

It also helped me take a step back and realize that sometimes I unconsciously stayed at jobs due to the continually changing (typically stressful) environment.