This paper’s authors argue that using GWP to assess the relative planetary warming  caused by various different sectors is therefore a deeply flawed metric. They propose that a better measure for policymakers to adopt would be something  called Effective Radiative Forcing, or ERF.

I use dashes -, for the reasons you mention above. I avoid underscores because they require using the shift key, so take at least twice as long to type (also, I think they're ugly)

With so many characters that you might not think should be special, in fact being special, I just use the special characters anyway. This also puts me in the good habits of using bash completion, where it will auto-escape all the special characters in a filename. But it also puts me in the good habits of escaping/quoting EVERYTHING in scripts and multi-part 1-liners in bash. For example, in just a simple 1-liner: for file in *.txt; do something.sh "$file"; done That way, even if one of the files has a space, or some other character, the do part of the loop will still act on it, and not miss on 2 or more file-name-parts, possibly causing unintended side-effects. Since I cannot control the space/not-space naming of EVERY file I encounter, and if I tried, it would probably break some symlinks somewhere, causing yet more unintended consequences, I just expect that all filename/directoryname could have spaces in it, and just quote/escape all variables to compensate. So, then I just use whatever characters I want (often spaces) in filenames. I even use spaces in ZFS dataset names, which I have to admit has caused a fair amount of head-scratching among the developers that write the software for the NAS I use. Sum-up: Spaces are not an invalid character, so there's no reason not to use them.

Some applications and computer scripts may not recognize spaces or will process your files differently when using spaces. A best practice is to replace spaces in file names with  an underline (_) or hyphen (-).

I've noticed somethings, particularly ADB commands, use spaces to issue the next part of the command. Thus having a space would say that there's a new command. And since hyphens are actually used in some spelling, such as my last name, it's better to use underscores.

I didn't see this mentioned, but lots of software doesn't treat the underscore as a word separator (also called a "break character") these days. In other words, you can't jump to next word with Ctrl+Right-arrow or select individual words by double-clicking on them. The argument is that variable names in some programming languages like Python use snake_case, so highlighting them might require an extra Ctrl+Right-arrow. I do not necessarily like that decision, because, while being (marginally) useful in those limited domains, it makes file renaming and any other word manipulations or typesetting very cumbersome.

But one thing to remember is that if you are primarily doing python coding - and your code tree has files/directories with hyphen in them and you intend to use them as modules (do an import filename in your code), then this will cause errors as python modules cannot have hyphen in them.

Underscores are usually the convention that people use when replacing spaces, although hyphens are fine too I'd say. But since hyphens might show up in other ways such as hyphenated words, you'll have more success in preserving a name value by using underscores. For instance, if you have a file called "A picture taken in Winston-Salem, NC.jpg" and you want to convert the spaces to underscores, then you can preserve the hyphen in the name and retain its meaning.

"we [Google] don't really care about underscore versus dashes."

I must be the exception, because I use both spaces and underscores, depending on circumstances.   The practical/obsessive-compulsive side of me saves all my documents using spaces. They're cleaner to read than underscores, and they look far more professional.   The programmer side of me still uses underscores in files that will be accessible via the web or that need to be parsed in a program.   And to complicate matters worse, I use camel case to name all my programming files. So in actuality I use 3 standards interchangeably.   Both have their uses, I just choose one for clarity and one for ease of use.

Separating each of these entities with a hyphen allows you to double-click and highlight only that entity. With underscores-only, you need to enlist the painstaking process of precisely positioning your cursor at the beginning of the entity, then dragging your blue selector to the end of the entity.

Albert Eckhout, which occupy a transitional space between the national type of the 16th and 17th centuries and the racial categories that developed in the 18th and 19th centuries.

7th century, the representation of skin color began to take on more importance, and engravings of Africans and Americans started to suggest differences in complexion.

zettelkasten faq

card index for business

concentration of ideas

Erich Fromm's zettelkasten

card index in literature

zettelkasten productivity

memory and history zettelkasten and memory

zettelkasten examples digitized examples personal websites as commonplace books

zettelkasten why

The function symbol notation is the least used notational system in jazz. As the namesuggests, this notation specifies the harmonic function of individual chords and evencomplete chord progressions. It has the potential of being useful to notate specificbehaviors of chords that may not—at least, not on the surface level—indicate that theybelong to a particular functional family of chords. As such, function symbols enable theperception of harmonic progressions from a more structural perspective. Function symbolsindicate neither the architecture nor the specific scale degrees of chords. This style ofnotation is more conceptual than it is representative of a specific surface event. The termssurface level and structural level are used to describe musical events and the degree oftheir importance. “Structural” events occur beneath the musical “surface” and areresponsible for the overall tonal, harmonic, and melodic forces controlling the piece.Function symbols use three labels: T for tonic-type chords, PD for predominant-typechords, and D for dominant-type chords.

Lead-sheet notation, also known as popular-music notation, is by far the most widespreadnotational convention used by jazz musicians. It comes in a variety of forms that arisefrom its murky origins and subsequent vague implementations. There are many alternatenotational systems in use, which for better or worse every jazz musician needs to getfamiliar with for purely practical, “bandstand” reasons. Here, we will only use chordsymbols that are commonly found in published and respected fake books. Lead-sheetnotation is very specific in showing what the chord is: it indicates the letter name, theexact number and types of extensions occurring within a chord, chordal inversions, orcomplex polychordal formations. A chord symbol, then, provides a quick insight into thechord’s pitch content. As such, it can be easily transmitted into a voicing that capturesthe essence of that symbol. The downside of this labeling is the lack of contextualconsiderations, especially in regard to the underlying tonality. As a tonally “uninterpreted”notation, we are not quite sure, for instance, how chords relate to one another, how theirbehavior conveys the underlying tonality, and what the overall tonal logic of differentchord successions may be.In this book, upper-case letter names will be used to indicate major-type chords. For minor-type chords a “min” extension following an upper-case letter name will be used. The lead-sheet symbols from Figure 3.6 also employ slash notation; this specifies a chord typewith the lowest sounding pitch separated by a diagonal slash. An upper-case letter nameto the right of the diagonal indicates the chordal root. The letter name to the left of thediagonal shows a specific chord type.

Figure 3.6 illustrates the structure of four triads and their inversions labeled with threesets of notational symbols: traditional lead-sheet notation above the staff, and Romannumerals and function symbols below the staff. Since we will use them interchangeablythroughout the book, let us make some general observations about their usefulness intheory and practice. Each of these notational conventions has unique advantages, but alsosome obvious shortcomings.

CamelCase is a way to separate the words in a phrase by making the first letter of each word capitalized and not using spaces

Editorial conventions may differ from publication to publication, but they are usually avariant of the so-called Leiden System. See Schubert, “Editing a Papyrus,” 203

Conventions are good, but they are very limited: enforce them too little and the programmer becomes coupled to the code—no one will ever understand what they meant once they are gone. Enforce too much and you will have hour-long debates about every space and colon (true story.) The “habitable zone” is very narrow and easy to miss.

Investors rarely try to break through a poison pill threshold, securities experts say, with the caveat that Mr. Musk rarely abides by precedent.

The above works great. However, the problem comes when I want to use literal types for my legal values. In my code, I want to do that so I can make sure I define a "handler" for every legal value: const legalValues = <const>["a", "b", "c"]; // later on... // Because legalValues entries are literal types, // I get a compiler error if I forget to define any behaviors const behaviors: { [K in typeof legalValues[number]]: any } = { a: something, b: somethingElse, c: anotherThing };

We also get a hook to alter commit messages so that they include a common suffix. We can then use this to set up a server-side hook that refuses changes that don’t have this in their messages.

Mutually exclusive categories can be beneficial. If categories appear several places, it's called cross-listing or polyhierarchical. The hierarchy will lose its value if cross-listing appears too often. Cross-listing often appears when working with ambiguous categories that fits more than one place.

RPython puts some constraints on the Python language such that a variable's type can be inferred at compile time.

Instead of one big code pile, activities will gently enforce a clean, standardized way for organizing code.

They are an abstraction that will save code and bugs, and introduce strong conventions.

The office door is locked at 5pm. We work hard, but at 5 it's time to go home!

Convention in Java, and I believe most other languages, is to use Listener suffix for historical reasons!

Handlers are normally not suffixed, but instead, they most often have on as the prefix (onClick, onSwipe etc.).

About the argument against it, "{@const will make code less consistent ": I think the same is true now, since people can come up with very different ways of dealing with the "computed value inside each loop/if function" problem. Some extract components, some use functions, some will prepare the array differently beforehand.

it also allows for more divergence in how people write there code and where they put their logic, making different svelte codebases potentially even more different due to fewer constraints. This last point is actually something I really value, I read a lot of Svelte code by a lot of different people and broadly speaking things look the same and are in the same places.

On the other hand, we could impose restrictions to the feature in order to avoid these hard paths.

Instead, my purpose is to illustrate why an alternative approach — based on Single File Components with real CSS — is so damn delightful.

By enforcing this practice, Svelte can make some assumptions that simplify your code.

often suppressing the very visual aids that mathematicians use to make their discoveries

kasper-netcdf.zip

I was so fed up of the mega amounts of boilerplate with Redux and the recommendation of keeping your data loading at view level. It seems to me that things like this, with components being responsible for their own data, is the way to go in the future.

Yet, a barful strife— Whoe'er I woo, myself would be his wife.

Analogous to this, there arc two things in every discourse which principally claim our aucntion, the sense and the expression; or in other words, the thought and the symbol by •. J. which ii is communicated.

Instead they would be dismissed as being a waste of a colleague's time, or as beside the point, or as uninformed, or simply as unprofessional. This last judgment would not be a casual one; to be unprofessional is not simply to have violated some external rule or piece of decorum. It is to have ig- nored (and by ignoring flouted) the process by which the institution determines the conditions under which its rewards will be given or withheld. These conditions are nowhere written down, but they are understood by everyone who works in the field and, indeed, any understanding one might have of the field is inseparable from (because it will have been produced by) an awareness, often tacit, of these con- ditions

This peace treaty brings in its wake something which appears to be the first step toward acquiring that puzzling truth drive: to wit, that which shall count as "truth" from now on is established. That is to say, a uniformly valid and binding designation is invented for things, and this legislation of language likewise establishes the first laws of truth.