Managing security teams is different in a lot of ways than other teams, but it's totally possible to structure and support them to better handle the pressures we're put under. Anyway, I wrote some of them down since I keep getting asked:
https://venturebeat.com/security/psychological-safety-is-key-to-managing-security-teams/
Golang HTMX Vite starter
https://github.com/gopherine/go-htmx-tailwind-vite-starter
Discussions: https://discu.eu/q/https://github.com/gopherine/go-htmx-tailwind-vite-starter
The starter uses, tailwind, htmx and golang. We are also using pinesui by devdojo which is built on top of alpinejs and tailwind - gopherine/go-htmx-tailwind-vite-starter
unpopular opinion/rant :
everytime there is a valid security concept that is born (Zero Trust, SIEM, detection engineering), it is very quickly taken, its meaning is emptied of anything relevant, and is used as a gateway to sell you bloatware platforms that don't really solve any of your problem, but the vendors tell you it's because you need to use them as a "single pane of glass" (other term for vendor locking) to really "unlock the potential" of the platform.
on top of that, you have the "vendors of vendors" that place the product in quadrant, triangle, pyramid or whatever magic form, in a category they defined themselves to serve the purpose of showing this or that product is *better*.
one rule of thumb : when an acronym was invented , not by a security researcher, but by a marketing/consulting company, there are high chances that the value it brings over what already existed is close to 0...
SASE,SSE,CASB,etc... 
thanks for reading my rant/non-ted talk
LeaKissner
Golang Weekly