1,457 karma · joined May 3, 2017
That is certainly in the less important end of the linting rules spectrum. Nonetheless, conventions like these add up in larger codebases in my experience. The more consistency you have with things that repeat a lot across the code improve readability quite much because the brain is able to do more chunking over time.
Of course this doesn't matter that much when you are learning a language or a framework and only have a couple of files.
As the link posted above mentions, you can alternatively use a timestamp-based prefix that wraps around after all the bits have been used. This one still leaks possible creation times of the record, so it's on par or better compared to UUIdv6, ULID, etc. (because here the exact creation time can't necessarily be deduced).
In all of these UUID solutions apart from the fully random v4, you are trading of the better index performance with some level of information leakage about the record the ID is associated with.
You mean just the regular E minor (triad)?
Anyway, there'a quite a lot of stuff on this site apart from this cheat sheet page: the chord page does indeed include inversions, e.g.: https://muted.io/c-major-chord/
They are easier to clean for sure but I can't believe the current "click this, slide that" UX is the best the manufacturers could come up with.
We've started planning a wedding recently and started drafting a guest list, which basically means making that hierarchy explicit on a spreadsheet (to filter out guests), only for two people at once instead. To my brain, which always wants to please everybody, it's a painful process.
.pico-enabled *:not(.piko-disabled) {
@import "layout/document"
@import "layout/sectioning"
@import "layout/container"
...
Then you can do this: <div class="piko-enabled">
...
<button>A button with Piko styling</button>
<div class="piko-disabled">
<button>A vanilla browser button</button>
... and any 3rd party components/elements etc ...
[1] https://github.com/picocss/pico/issues/31#issuecomment-91399...Well, I'm asuming we are talking about PRs against some protected branch where manually pushing changes directly is forbidden.