I recently hired into a data analytics team for a hospital, and we don't have a style guide. Lots of frustration from folks working with legacy code...I thought putting together a style guide would help folks working with code they didn't write, starting with requiring a header for SQL scripts first as low hanging fruit.

Or so I thought.

My counterpart over application development says that we shouldnt be documenting any metadata in-line, and he'd rather implement "docfx" if we want to improve code metadata and documentation. I'm terrified of half-implementing yet another application to further muddy the waters--i'm concerned it will become just one-more place to look while troubleshooting something.

Am I going crazy? I thought code headers were an industry standard, and in-line comments are regarded as practically necessary when working with a larger team...

As an enthusiast that takes portraits, travel, some macro, some wildlife, and a desire to do more sports and birding; I've always wanted to upgrade my SL1 to a full frame sensor/mirrorless.

Price is a big deal for me, and I want to buy once cry once--i want a camera that will last me the next 8+ years. Reviews on the RP look great, and I don't pretend to be an expert--im confused though, because while the R6 mkii has a few nice features I can't see why it costs ~twice~ as much. Is the R6 mkii worth the upgrade, and/or will it be more future proof?