Sure, you seem intent on making a point that has nothing to do with OP's assertion or my observation, so go for it. (That's a strawman fallacy, right?)
I was not highlighting the author's background to appeal to authority. I was pointing out that what OP dismissed as "coder philosophy drivel" (likely from skimming the title and nothing else) was written by someone who has nothing to do with that field.
In fact, by doing that, OP made an anti-appeal-to-authority. You seem to be interested in logical fallacies.. could you help me out and tell me if that one has a specific name?
I wasn't making a value judgement on the piece (or the author's credentials). My point was that someone took the time to share something with the world and you dismissed it after making (incorrect) assumptions about their background. You'll miss out on a lot of good stuff if you've already cast judgement before you finish reading the title.
In any case, it's a <3min read and it does offer a few non-BS pieces of advice that may be useful to some.
It looks like it is using the "Tufte" style, named after Edward Tufte, who is very famous for his writing on data visualization.
More examples: https://rstudio.github.io/tufte/
Gotcha; never been subject to gardening leave myself, but I always assumed it exists for the same purpose as a noncompete, i.e. to provide a 'cooling off' period to lessen the competitive impact that the exiting employee can have by switching to another firm. I assumed that since it's been around a while in finance that the "paid noncompete" idea became a negotiated part of the comp.