The solution is to record an #HPREp on the topic of sonar.properties (and -D parameters, same thing) and its mapping to the UI project settings and to docs.sonarqube.org/latest/projโฆ and then send anyone who asks to that episode and its shownotes.
I learned git by using it for 15 years and reading man pages, so I don't have personal recommendations. I am however conducting git workshops in the office and once I've found a form that doesn't scare people I may create a series of #HPREp from that. If and when I do I promise to come back here and post links.
The most interesting feature included is PEP 622 -- Structural Pattern Matching https://www.python.org/dev/peps/pep-0622/ , similar to Scheme's (match), but a bit less powerful and spelled in Python. That's worth an #HPREp.
The most interesting feature *not* included was PEP 563 -- Postponed Evaluation of Annotations https://www.python.org/dev/peps/pep-0563/, which was slated for inclusion but was pushed to 3.11 to sort out some details regarding libraries like Pydantic that rely on reflection on declared types.
Now, the hoops I tried to jump through to simply create this file, and the various caveats, merit a small #hprep .
I didn't want to use `dd if=/dev/urandom`. I ended up using `dd if=/dev/urandom`. Short version:
- No zpool shrinking - No fallocate on ZFS - dedup or compression defeat /dev/zero - Bonus issue: Be careful with your block size when reading from /dev/urandom
The git aliases I wrote to handle git worktrees and submodules to save bandwidth when working on the other side of the world with a 100 Mbps internet router in the office and crappy HK peering on my side
Wow, #hpr New Year's part 2 has so much great discussion, and I've been thinking 2-3 times already (and I'm only 1h in) "well that merits an #HPRep of its own".
My hands have been busy with chores while listening, so I'm going to have to listen to this again at high speed and note those things down.
@dthompson @catonano @pho4cexa I don't think it's a problem that languages have their own language-specific infrastructure, in fact I think it's a good thing, as long as it's made to cooperate well with distribution infrastructure. I have a long, half-unwritten post about this that will probably become an #HPRep .