A header might be useful, although there’s likely better ways to (not) document what each sql statement does.
But inline documentation? I’d suggest trying to work around that. Here’s an explanation as to why: https://youtu.be/Bf7vDBBOBUA
If possible, and as much as possible, things should simply make enough sense to be self documenting. With only the high level concepts actually documented. Everything else is at risk to be outdated or worse, confuse
No sure about 64gb, but for performance/watt and reliable Linux I can really recommend the Amd p16s and t16(s?) machines from Lenovo. Have about seven in the office and they are excellent.
I too, as someone in devops, am wondering what you need that much memory for. Do you simply really like VMs? :)
Also, have you considered doing the really heavy stuff remotely? Whenever I need desktop type power (16 physical cores and 128gb memory) I simply wake the desktop, ssh into it and do it there.
I had an extreme, as nice as it was it kind of sucked on Linux due to all the dual gpu weirdness (working hdmi or battery longevity, pick one)
Has this changed recently? Because it used to be due to the wiring of hdmi though the external gpu
Although a bit long, I do like this almost impossible to ignore example of self documenting code :)