Most developers just have a linear view of git, which is fine. Should I really care that origins are just named nodes on combined graphs? Like, I just want to check in my code before I have to merge someone else's.
Know the rules, fight the rules, I guess. More readable, but I’ve since regressed as tooling comes into play. Maybe it’s a good way to still use ems and differentiate from AI.
I am personally a fan of space padded em-dash. Visually, semantically, it makes sense on all modern planes. There's an argument for line-break parsing.
Of course I recommend do-not-adopt, think Roman-cart-wheel-axle-width reasons.
Author failed to explain the dash universe and their semantic assignments.
- em dash: adjoining thought (Hey, so — <declaration>)
- en dash: expresses a range (1–100)
- dash: compounds word-parts (Sarbanes-Oxley)
I'd also like to see more concise philosophy around em v. ellipsis, "limerance" is poetic (and ironically antithetical to this "essay" … and what of parens?). In short, em is communication and ellipsis is personal.
I offer this feedback as a humorously offended fan of all sidecar prose (dash, ellipsis, parens, quotes, and meta typographical treatments) pre-AI era.
Finally, I'd love to hear from this author regarding modern use of period in modern comunication, with canonical use-case of bulleted list as example.
Yah you get this inner platform effect where designers start unwittingly creating their own version of css using Figma and it gets really bespoke really fast.
I was making a new brand file in Figma and was about to define all the variables and aliases, paths, all that. Took one look at it and just made the 8 colors I needed and went on with the design.
TLDR: practice. If you have sufficient natural talent xor will, you will eventually go past the canon of available material and begin to transcribe your own. Then there are those who move to creation, either immediately or somewhere in the path.
Zero rebases since Fable 5.