Please use $needle in a $haystack idiom in your example. It's much easier to read and understand.

This follows on a fairly widespread practice in various programming languages to use a leading underscore to indicate that a function or variable is in some way internal to a library and not intended for the end-user (or end-programmer).

Thus, the New York Public Library has CATNYP.There is BEARCAT (Kutztown University) and ALLECAT (Allegheny) andBOBCAT (NYU’s Bobst Library) and CATS (Cambridge). There is VIRGO(the University of Virginia), FRANCIS (Williams College), LUCY(Skidmore), CLIO (Columbia), CHESTER (the University of Rochester),SHERLOCK (Bualo State College), ARLO (the University of Colorado atColorado Springs), FRANKLIN (the University of Pennsylvania), andHarvard’s appropriately Eustace Tilleyish HOLLIS. There is BISON(SUNY Bualo), OASIS (the University of Iowa), ORION (UCLA),SOCRATES (Stanford), ILIAD (Butler), EUCLIDPLUS (Case Western), LUMINA(the University of Minnesota), and THE CONNELLY EXPLORER (La Salle).MELVYL (the University of California system) is named after MelvilDewey; the misspelling was reportedly intentional, meant toemphasize the dierence between Dewey’s cataloging universe andour own.

Okay folks. I think I better name my antinet before he gets too big and people start getting suspicious. After some thinking and googling words I don't know in order to make an acronym I think I've decided on "J.A.K.O.B". Which stands for "just a knowledgeable omnilegent box". Omnilegent apparently means reading or having read everything. The name is of course inspired by J.A.R.V.I.S (just a very intelligent system) the artificial intelligence created by Tony Stark.

Zettelkasten in one or several language(s)? .t3_15wo3f2._2FCtq-QzlfuN-SwVMUZMM3 { --postTitle-VisitedLinkColor: #9b9b9b; --postTitleLink-VisitedLinkColor: #9b9b9b; --postBodyLink-VisitedLinkColor: #989898; }

It may seem like Testing is some sort of beta, unstable version but that’s not entirely true. Debian Testing is the next Debian stable version. The actual development branch is the Debian Unstable (also known as Sid). Debian Testing lies somewhere in between the unstable and stable branch where it gets the new features before the stable release.

Random::Formatter#from_set(set, n = 16) (or Random::Formatter#from_set(n = 16, set: …))

But I wouldn't call them a ZK® (stealing Andy's shorthand!) but they were a box of notes (Zettelkasten?).

It is unfortunate that the German word for a box of notes is the same as the methodology surrounding Luhmann.

MyServiceController

There was an additional appeal to the name: Many of the Mandarin-speaking Connies I spoke to pointed out that the Mandarin for “healthy girl” — 康妮 “kang ni” — sounds an awful lot like Connie.

Finding good names is quite difficult. Single words are also almost always better than combined names, even though one is a bit limited with single words alone. There are exceptions though. For example .each_with_index or .each_index are good names, IMO.

my Zettelkasten is named "House of Pomegranates", after my favorite Oscar Wilde short story collection.

The ID suffix was added because I use external tools to add notes to my vault so I needed a means to ensure there would never be a collision. For example, Alfred. If I accidentally typed the name of a note that already exists into it I didn’t want it to accidentally overwrite an existing note,

The Compass of Zettelkasten Thinking.

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

For those who can hear. When you name you divide. There is zero biblical precedent for naming a certain group of believers .... Identify with the body of Christ in your area .... We are exhorted to, "let there be no division among you".The only use of "churches" plural in scripture refers to the church in different locations. There was no such thought of "churches" within one locality. Love you all and pray more will see this so the world may see we are one and know that Jesus was sent by the Father.It's important John 17:20-23

no need any name whatsoever bro It's who we are that's important.

Often it helps to have the location or region in the name, a mountain near you or the name of the valley you are in, or a creek, stream or river. What says 'home' about where you are?

Pleeaasse don't give "it" a name.There is no "it". You believers are part of the church in your location and you meet together.There is zero biblical precedent for a group of believers giving their particular group a name.I understand that nearly all believers do .... That in no way makes it right.Names seperate us from others of the church in our area.

Paul TrosclairHow is it biblical to name a church ?2wBeth BalmesPaul Trosclair geographical. E.g.Church in Corinth. Church in Ephesus.2wJohanna WhittakerBeth Balmes .. Paul's letters were to the CHURCHES (ekklesia) in ...

The lowest strata represents Generative ambiguity. Here, words are used as symbols for ideas that are very hard to express; an individual gives a name to a nebulous collection of ideas or thoughts. They struggle to make this approach make sense to others.

It acts as a black hole null object, allowing arbitrarily deep method chains.

For any message that has not explicitly allowed or expected, the double will return itself.

to make the double "loose"

Tinderbox

Title for My Book

The vendor prefix (vnd.) indicates that it is custom for this vendor.

The +json indicates that it can be parsed as JSON, but the media type should define further semantics on top of JSON.

Wikipedia would not be as successful as it is now had I named WikiWikiWeb "electronic-encyclopedia"

Slab

OpenBooks is a hub for Neocities community projects.

Protagonist Does a Thing formula

Are there relevant IPs buried in other projects you’ve worked onin the past?

Douglas Adams noted, "Capital letters were always the best way of dealing with things you didn't have a good answer to."

By capitalizing words that shouldn’t be, it sounds as if the writer is trying to inflate the importance of those words artificially.

We should ask the PM to chime in and post it in #naming on Slack.

The HTMLLabelElement.htmlFor property reflects the value of the for content property.

Is the name "delegated type" up for review? I don't see any delegation happening in the code. It looks more like a "subtype", or "secondary type", or something like that.

Unfortunately, I think a lot of the answers here are perpetuating or advancing the idea that there's some complex, meaningful difference. Really - there isn't all that much to it, just different words for the same thing.

'method' is the object-oriented word for 'function'. That's pretty much all there is to it (ie., no real difference).

It might be confusing that a union of types appears to have the intersection of those types’ properties.

serverFetch name is unclear. That the docs need to say in bold that it's external is a bit of a code smell.

Rename to externalFetch. That it runs on the server is already implied by it being located in hooks

I feel like app/packs (or something like it) is a good name because it communicates to developers that it's not just JavaScript that can be bundled, it's also CSS, images, SVGs — you name it. I realize what can be bundled is wholly dependent on the bundler you use, but even esbuild supports bundling CSS. So couldn't this possibly be confusing?

arguments = method_proc.parameters.map(&:last)

“System tests” is a common naming for automated end-to-end tests in the Rails world. Before Rails adopted this name, we used such variations as feature tests, browser tests

(In case you’re wondering, there’s nothing special about the name CSRF-TOKEN.)

(I think you need a better name than private_accessor though)

I worked in the word "Mancunian" three times in one short paragraph. It was the second-best demonym r d ever heard, almost match-ing Vallisoletano (a citizen ofVallado-lid).

fetch: fetcher

(name subject to bikeshedding)

µ

die-hard fans of filter-branch may be interested in filter-lamely (a.k.a. filter-branch-ish), a reimplementation of filter-branch based on filter-repo which is more performant

1. The main folder names have numbers in front of them, such as 0-base to ensure that the folders stay in that particular order. You can certainly omit this or choose different folder names.

For those who are wondering about the name, Bear Raid is a real phrase used to describe when a stock price is intentionally lowered through short selling and rumors.

Around &Bigger the box is bigger: 75mm high instead of 45mm or so.That was the main reason for the name &Bigger. The first edition does fit in its box but very tight. Because the first factory used bigger cardboard than planned. They told me about this "upgrade" after they produced the game. The thicker tiles (about 2.5mm) did feel good for the game so the &Bigger edition has the same

antimicro is a graphical program used to map keyboard keys and mouse controls to a gamepad.

The absence of a method name here is per design: this object does only one thing, and hence what it does is reflected in the class name.

As we know, naming is hard.

Another thing I don’t like is the name of the config file manifest.js. Internally Sprockets has the concept of a manifest already Sprockets::Manifest, but the two aren’t directly coupled. We also already have a “manifest” JSON file that gets generated in public/assets/ and has manifest in the name .Sprockets-manifest-140998229eec5a9a5802b31d0ef6ed25.json. I know one is a JS file and one is a JSON file, but it’s a bit confusing to talk about.

The link name is not very helpful, it doesn’t explain what it does very well.

Most C++ template idioms will carry over to D without alteration, but D adds some additional functionality

There are two definitions of ‘Enterprise’ 1 - Enterprise as a business. In fact, in French, ‘enterprise’ literally means ‘business’ 2- Enterprise as a large business. This is the most common use of the term in business, differentiating between small, medium, and large businesses. In this context, there is no official rule, however it is generally accepted for enterprise to mean companies with over 1,000 employees and/or $1B in revenue

termini (or “ends” as we used to call them).

outcome.valid?

if outcome.success?

value returned from #execute

By convention, we call this an outcome

Call .run on your interaction to execute it.

Hopscotch

if you name you instance variable form, then you can always just pass in params[:form]

Why process, not save? This is entirely up to you. However, it's good to stay consistent across your team so there's no confusion. I began using save but found there are some cases for forms where you aren't saving anything, such as when you are just triggering a job or push-notification. I found using process fits more cases so that's what I use. This is also typically the only method that is public on my forms.

@conference_form.submit(conference_params)

    @conference_form = ConferenceForm.new(conference)
    @conference_form.submit(conference_params)

    if @conference_form.save

Unlike naming children, coding involves naming things on a daily basis. When you write code, naming things isn’t just hard, it’s a relentless demand for creativity. Fortunately, programmers are creative people.

If we renamed things more often, then it probably wouldn’t be so hard to name them in the first place.

We also find it hard to agree on what good names and bad names look like, which makes it hard to know when renaming improves a name.

This is funny because it’s unexpected. Cache invalidation sounds like a hard thing, while naming sounds more straightforward. The joke works because it violates our expectation that hard things should be technical. It’s also funny because it’s true.

First of all, we want names to exhibit truth and beauty: to be the right names, and to make our code clean and beautiful. At least, this is what we want to think about our code, but naming’s importance is far more practical.

Naming is communication

Naming matters for both idealogical and practical reasons.

Naming is just one part of the micro-design activity that we call programming. If design weren’t hard, we wouldn’t find good design so satisfying.

Anyone who has ever tried to name a child knows that naming is hard. Naming things in code is harder. It’s bad enough that you have to commit to a name that someone isn’t going to like. You also have to be able to live with it.

There’s only one hard thing in Computer Science: human communication. The most complex part of cache invalidation is figuring out what the heck people mean with the word cache. Once you get that sorted out, the rest is not that complicated; the tools are out there, and they’re pretty good.

When you use this syntax the lines on either end of the areas are actually getting named automatically.

Notice that you’re not naming lines with this syntax, just areas.

Is store the right name? (session?)

Maybe something more neutral just meaning a virtual element / no-element container would better express the intention? And regarding the syntax, maybe it would also feel less repetitive / boilerplaty than <svelte:slot slot="name" />... Maybe something like <svelte:fragment slot="name"> or <svelte:virtual slot="name">?

Also agree that <svelte:slot> is perhaps a little confusing since it replaces the slot attribute rather than the slot element, so <svelte:fragment> would make more sense

Just to reiterate the discussion on the RFC, there was a suggestion that we change <svelte:slot slot="foo"> to <svelte:fragment slot="foo">, since it's the counterpart to a <slot> rather than an equivalent to it

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.).

Listeners are often objects, so they are commonly suffixed with Listener.

The Object.getPrototypeOf() method returns the prototype (i.e. the value of the internal [[Prototype]] property) of the specified object.

Microsoft announced IronRuby, which uses the same name as Wilco Bauwer's IronRuby project with permission.

@import is also a CSS feature, and the differences can be confusing

We could potentially have another flag that was your definition of dirty, but then we run into the hard problem in computer science: naming things.

In a browser, deep-diff defines a global variable DeepDiff. If there is a conflict in the global namespace you can restore the conflicting definition and assign deep-diff to another variable like this: var deep = DeepDiff.noConflict();.

I vote for calling it let Could be used like this {#let foo = initialValue}. It's closer to javascript

I expressed doubts about the name with because of its existing meaning in javascript, which is a fair point from my past self.

The other module on npm that I found to do this

For event listeners we support the standard jsx naming convention onEventname (this is converted to on:eventname in svelte) as well.

their name gives no mnemonic boost whatsoever. Whatever faint associations it might once have held fade away, especially when the discover was neither famous nor narrow, and the reader is several generations removed.

The worst answer I can imagine is the one Pope Gregory VII gave for refusing to let the Holy Scripture be translated out of Latin: “... [I]f it were plainly apparent to all men, perchance it would be little esteemed and be subject to disrespect; or it might be falsely understood by those of mediocre learning, and lead to error.”

remaining: 0, callbacks: [] r: 0, // remaining outros c: [], // callbacks p: outros // parent group

Why the obfuscation of remaining to r and callbacks to c? This is fine for function-local variables but in this instance makes the code significantly harder to reason about? There is no notion of what c and r mean.

But I just want to say npx is lame. It should have been npm run or npm exec or something.

The problem I have with this approach to state and prop variables is that the difference between them is very blurry. In React you can clearly see that a prop is an input to component (because of clear function notation), and that state is something internal. In Svelte they are both just variables, with the exception that props use export keyword.

if this does land, my vote is for smoosh

For the actual name of the thing, I like behaviors more than enhancers. That might be too limiting but I can't think of using this for styles or something that I wouldn't call a behavior. traits is also nice. Hey, decorators works too.

While there is some precedence in other frameworks for using as, the word doesn't fit well. Since you are adding functionality to elements I like the word add better (and it only has 1 more character).

I like use. But we would still need a noun to reference them by in the docs or libraries.

What do you think of one of these: "actions", "enhancements", "additions" or "extensions"? My vote goes to "actions". It is short but it has meaning, as do the others.

one problem with 'behavior' is that's the terminology we use to describe all of a component's encapsulated logic — methods, transitions, etc.

To differentiate <style scoped> from the existing top-level <style> elements, I propose that we refer to these as 'local scoped styles'.

The above doesn't work for another unfortunate reason, it's not possible to write export let class = ''; instead CustomComponent because class is a reserved keyword and isn't allowed to be used as a variable name. The workaround would have to be to use some other prop name like maybe cssClass but then there's no "standard" by which all Svelte components can follow and every library will choose a different name which is cumbersome for users, because it creates scenarios like:

It was called a "virtual DOM" library because it didn't start out as isomorphic, but actually tied to the DOM from the start. It was an afterthought to make it isomorphic.

Is it “syncthing”, “Syncthing” or “SyncThing”?¶ It’s Syncthing, although the command and source repository is spelled syncthing so it may be referred to in that way as well. It’s definitely not SyncThing, even though the abbreviation st is used in some circumstances and file names.

To follow conventions of naming across GitLab, and to further move away from the build term and toward job, some CI/CD environment variables were renamed for GitLab 9.0 release.