2 ms·
I like the 2 examples. Tailwind has multiple traits that make it a winner, and I think that "never naming anything" is a secret super-power it has. You don't re
by nichochar 2y ago
I like the 2 examples. Tailwind has multiple traits that make it a winner, and I think that "never naming anything" is a secret super-power it has. You don't realize it, but it just makes coding easier over time. Compare to styled-components, which also has css-in-the-same-file-and-localized-context, the naming alone makes using it less productive.
For git, I'd never even considered it, but I often find myself renaming branches `thing-im-doing2` just because the first branch is broken, or having `abc-def` and `def-abc` branches accidentally...
The tooling needs to be wildly adopted though, and that's difficult. I gave up on graphite for exactly this reason.
- positr0n 2y agoI do the opposite and rename the current branch `thing-im-doing-borked` then fix it and reuse the old name with `git checkout -B thing-im-doing`.