if I send you a Google doc and we start all collaborating in the same same thing and it's amazing we're sharing all this data um it's kind of silly that we have to move the updates through the backb to some server out there and shipping them back here when we now have really sophisticated algorithms that can do um you know smart Conflict Free resolution that allows us to collaborate in real time and yet we're still moving all the updates to the backbone right this is very silly and it gets worse when you think about the network falling apart

If I decide to add it, which solution should I pick, battle tested Sorbet or core team endorsed RBS?

The Buzz for deafness

when I'm referring when we refer to the fourth turning of the Dharma we're we're kind of we we're really using a a Buddhist model but it can be but it's a but it's a universal model

used to be

This is the most simulative version of a controller. It will try and mimic real user behaviour. It's the recommended version to use when the goal of the load-test is finding out how many concurrently active users the target instance supports.

this propaganda plays on psychological structure and if you're able to fish into that you're able to exploit those irrational Tendencies

It was enclosed in scare quotes, a sort of acknowledgment that the author knew it was non-standard, but was too apt for the purpose to resist. I remember reading it and trying to think of the “real” word that would be employed there, but could not find a satisfactory alternative. Since then, I’ve found myself unable to resist using the word when appropriate, due to its utility!

Who says it's not a word? Not a word, simply because lexicographers have not recognized it? When a lexicographer recognizes it, it has already been in use! Even Mr. Fiske says it is a word, although he obviously disprefers it.

on reasonable uses of "disprefer" — it's probably true that its meaning is not immediately apparent, and using it when addressing general audiences probably avoided (dispreferred?), but of course, it depends on the context I think. It is a term that has an obvious jargon aspect, but that doesn't seem to me to make it uniformly verboten. Other, DNA would never have entered the popular lexicon, or quantum… I'm sure those parallels are inapt in several ways, but my point, which I think still stands, is that while clarity to the broadest audience possible is often a laudable goal, this also doesn't mean it should be the only or always the chief goal. It seems to me technical words get disseminated and incorporated popularly through their use outside of strictly technical fora, and while several people said they did a double take or didn't immediately understand the word (or misunderstood its meaning), it's also true that this can happen with perfectly reasonable, standard vernacular constructions, especially reasonable standard constructions that are expressing a counter-intuitive (even if true) claim. Just sayin' — "can people understand this without giving it but a moment's thought" is a high (or ultra-low) car to hold all non-technical communication to. (That said, I also have a love for arcane words, shades of meaning, and being able to express certain moods/valences/concepts precisely. THAT said, I'm no linguist, and probably won't be using this word commonly for all my talk.)

The main problem with disprefer is that it violates de Buitléir's rule: If *I* use a word you're not familiar with, your education or experience is lacking. If *you* use a word I'm not familiar with, you're being a show-off or making up words.

Instance methods Instances of Models are documents. Documents have many of their own built-in instance methods. We may also define our own custom document instance methods. // define a schema const animalSchema = new Schema({ name: String, type: String }, { // Assign a function to the "methods" object of our animalSchema through schema options. // By following this approach, there is no need to create a separate TS type to define the type of the instance functions. methods: { findSimilarTypes(cb) { return mongoose.model('Animal').find({ type: this.type }, cb); } } }); // Or, assign a function to the "methods" object of our animalSchema animalSchema.methods.findSimilarTypes = function(cb) { return mongoose.model('Animal').find({ type: this.type }, cb); }; Now all of our animal instances have a findSimilarTypes method available to them. const Animal = mongoose.model('Animal', animalSchema); const dog = new Animal({ type: 'dog' }); dog.findSimilarTypes((err, dogs) => { console.log(dogs); // woof }); Overwriting a default mongoose document method may lead to unpredictable results. See this for more details. The example above uses the Schema.methods object directly to save an instance method. You can also use the Schema.method() helper as described here. Do not declare methods using ES6 arrow functions (=>). Arrow functions explicitly prevent binding this, so your method will not have access to the document and the above examples will not work.

In API design, exceptional use cases may justify exceptional support. You design for the common case, and let the edge case be edge. In this case, I believe lib deserves ad-hoc API that allows users to do exactly that in one shot:

I think we are a victim of behavioural norms and so many of the apps that I use have this pattern. That's not to say it's the right behaviour, but it may be hard to break the pattern for users.

I feel insanely chuffed at recognizing scarce and desirable works that have been overlooked or underpriced. I once paid $5 for an inscribed first edition of Zora Neale Hurston’s “Tell My Horse” in a very good dust jacket. Try to find a like copy today.

Books aren’t commoditiesAdvertisementI despise — viscerally, perhaps irrationally — the people one sometimes sees at used book stores scanning every title with a handheld device to check its online price. They regard books strictly as products and usually don’t know anything about them, only caring about what they can buy low and sell high on Amazon or eBay.

Donald Trump has Sonny Bono beat as a kind of used-car salesman.

Grading guidelines New. Item is brand new, unused and unmarked, in flawless condition. Protective wrapping should be intact. No blemishes on the outside cover. Stickers/marks indicating it may be “bargain” or “remainder” should not be considered new. Used: Like New. Item has very few defects and looks as good as new. Some minor blemishes and/or remainder marks are acceptable for this condition.   Dust cover/outside case (if applicable) should be intact.   Pages: No marking or highlighting of any kind. Shrink wrap: May be opened or missing for standard bound items. Loose leafs should be shrink wrapped to ensure all pages are present. Supplemental materials: (e.g.) CDs, DVDs, access codes should be unused. Used: Very Good. Items may have some minor defects such as marks, wear, bends, spine and page creases. Dust covers/outside case may be missing. Supplemental materials: May be missing. Water/stains: No water damage or stains of any kind acceptable in this condition. Pages: Very minor writing or highlighting (a few pages) OK. Personalization: No library labels acceptable in this condition. Name written inside OK. Binding/covers: Minimal blemishes and slight defects acceptable. No missing or loose pages. Loose leafs should be wrapped or rubber banded together and all pages must be present. Used: Good. Items with moderate wear and tear. Binding and pages should be intact. Covers: Can have curl and small creases. Moderate scuff marks or small cut OK. Corners: Can have some damage, light (1-2 inches) peeling OK, some (25%) bend OK. Pages: Minor highlighting (~20%) OK. Dog ear folds on page corners OK. Water/Stains: No visible water/spill damage. Minimal stains OK. Supplements: Can be missing/opened, unless the ISBN is a stand alone access card or a bundle edition (book with access code). Personalization: Name written inside or library labels OK. Binding: Moderate wear is OK, no loose pages. Loose leafs should be wrapped or rubber banded together and all pages must be present. Used: Acceptable. Items with more than moderate wear and tear. Binding and pages should be intact. Pages: Should be readable. Moderate highlighting and writing OK (more than ~20%). Water/Stains: Minor water/spill damage OK. Binding: Heavy wear OK, must still be intact, no loose or missing pages. Used: Unacceptable. Cover: Cover not intact. Cuts going through the cover into multiple pages. Page damage: Lines unreadable from highlighting. Page completely torn (part of page is missing) or major partial tear (high probability that normal wear and tear during next usage will result in part or all of page falling out). Water damage: Pages swollen, major wrinkling, excessive stains, major discoloration or moldy (foxing). Mismatch ISBN: Submitted ISBN does not match ISBN of what was received. Stickers or Tape: Used deliberately to hide markings specific to instructor, international, and sample editions, which are all deemed unacceptable. Rebound items. Binding: Pages are separating from binding or have been fixed with tape.

The problem is that the caller may write yield instead of block.call. The code I have given is possible caller's code. Extended method definition in my library can be simplified to my code above. Client provides block passed to define_method (body of a method), so he/she can write there anything. Especially yield. I can write in documentation that yield simply does not work, but I am trying to avoid that, and make my library 100% compatible with Ruby (alow to use any language syntax, not only a subset).

fragments_shored · 1 hr. agoI don't have a specific edition to offer, but you asked "why don't publishers publish more books with scholar's margins?" and the answer is because it's expensive. More white space means more paper and binding material, longer time for the print run, more customization on the press, heavier and therefore more costly to ship. Book publishing operates on a very thin margin so it's not cost-effective, especially when most consumers don't care about the extra margin space and/or aren't willing to absorb the costs in the purchase price.What can consumers do to encourage publishers to change these practices? Be willing to spend the $80 for the scholar's margins instead of expecting to pay the normal $5 to $10.

Interestingly, Rails doesn't see this in their test suite because they set this value during setup:

Drum or bag – a mechanism that requires replacement of the drum or bag that collects the matter.

I am firmly convinced that asserting on the state of the interface is in every way superior to asserting on the state of your model objects in a full-stack test.

The more your tests resemble the way your software is used, the more confidence they can give you.

In April 1863, Carleton gave orders to Colonel Kit Carson to round up the entire Navajo population and escort them to Bosque Redondo. Those who resisted would be shot. Thus began a period of Navajo history called the Long Walk, which remains deeply important to Navajo people today

sinful

devout

alas!

targeting what the user actually sees

The most important guideline to give is the following: Write clean unit tests if there is actual value in testing a complex piece of logic in isolation to prevent it from breaking in the future Otherwise, try to write your specs as close to the user’s flow as possible

It’s better to test a component in the way the user interacts with it: checking the rendered template.

Introduce behaviour that is likely to surprise users. Instead have due consideration for patterns adopted by other commonly-used languages.

We are are continuing our commitment to creating our games that are free and widely accessible anyone that is curious by making our game files available under Creative Commons license BY–NC–SA 4.0. That means we will continue offering a full, free print-and-play kit for Pax Pamir, and later this campaign, John Company! Anyone can use, remix, and share the game, so long as they do not use it for commercial purposes. 

A generic trademark, also known as a genericized trademark or proprietary eponym, is a trademark or brand name that, because of its popularity or significance, has become the generic term for, or synonymous with, a general class of products or services, usually against the intentions of the trademark's owner.

has been downloaded nearly four million times worldwide across both app stores

Software that is not currently being used gradually becomes unusable as the remainder of the application changes.

Infrequently used portions of code, such as document filters or interfaces designed to be used by other programs, may contain bugs that go unnoticed. With changes in user requirements and other external factors, this code may be executed later, thereby exposing the bugs and making the software appear less functional.

Another important MicroJS attribute is independence. Ember, Backbone—even Bootstrap to a degree–have hard dependencies on other libraries. For example, all three rely on jQuery. A good MicroJS library stands by itself with no dependencies. There are exceptions to the rule, but in general, any dependency is another small MicrojJS library.

In production, you will never trigger one specific callback or a particular validation, only. Your application will run all code required to create a Song object, for instance. In Trailblazer, this means running the Song::Create operation, and testing that very operation with all its side-effects.

There’s no need to test controllers, models, service objects, etc. in isolation

Run the complete unit with a certain input set, and test the side-effects. This differs to the Rails Way™ testing style, where smaller units of code, such as a specific validation or a callback, are tested in complete isolation. While that might look tempting and clean, it will create a test environment that is not identical to what happens in production.

found that using only the Pascal-provided control structures, the correct solution was given by only 20% of the subjects, while no subject wrote incorrect code for this problem if allowed to write a return from the middle of a loop.

Operations don't know about HTTP or the environment. You could use an operation in Rails, Hanami, or Roda, it wouldn't know.

The spelling "internet" has become often used, as the word almost always refers to the global network; the generic sense of the word has become rare in non-technical writings.

Well, a click funnel is basically an online sales funnel, but it’s widely referred to as a click funnel due to the growing popularity of the software called “Clickfunnels”.

If a reviver is specified, the value computed by parsing is transformed before being returned.

Google Archive Where old projects go to retire.

Secondary buttons are the ‘go back’ to the primary button’s ‘next’, or the ‘cancel’ button to the ‘submit’ button

Many linguists believe that the natural language a person speaks affects how they think. Does the same concept apply to computer languages?

text-overflow: ellipsis (married with fixed width and overflow: hidden

All validators can be used independently. Inspried by functional programming paradigm, all built in validators are just functions.

FormValidation.validators.creditCard().validate({

FormValidation.formValidation(formElement

The reason for this is very simple: once code gets checked-in, it takes on a life of its own.

Checking in is akin to sharing your code with others, and once out in the world, it’s hard to predict what that code will do.

that does not mean that I am advocating the other extreme–i.e., a templating language that allows a lot of logic. I find such templating languages, especially those that allow the host programming languages to be used inside the template, to be hard to read, hard to maintain, and simply a bad choice.

and one which you don’t need to use and won’t add any code to your app if you choose not to use

And of course, if you don't use them you don't pay for them

Passing the class prop to the root dom element is already a wide spread practice

It's a convention in Svelte to export { className as class } inspired from docs, but it's certainly not required by the compiler, so I don't think the class:directive can/should be assumed here.

On the one hand, it's an unofficial but widely-used practice to do let classNames=''; export { classNames as class }; in components and then apply that class on the top-level DOM element in the component. On the other hand, there are plenty of components out there that don't use this idiom

The old mydata and the new mydata are actually the same physical object (only the object’s internal value changed)

require 'minitest/autorun' class BugTest < Minitest::Test

For a non-monorepo package you can simply point directly to the Github repo. This case is similar, but you want to scope it just to a single package within the repo. For those that make monorepos they don't necessarily need this feature. It's for those that use projects that use monorepos. Telling them to not organize their projects into monorepos doesn't help people who make use of these projects.

If npm installs a git repo, it assumes that the git repo is the package. I don't really know how we could specify a sub-path easily, since all parts of the git url are already used for other things.

This is more a rhetoric question as this seems to be quite hard ;-) There is a long discussion about installing a subfolder of a repository and monorepos in general at the NPM Github issues (yarn misses this feature, too). The thing is that this makes it quite hard to report issues of your project as one can't test the current master easily. Do you recommend a way how to use the latest Github version?

Finally, the third, often forgotten, situation is that of a slanderer who makes unfavourable but true comments about another without any valid reason for doing so.

Used By

"neutrino-patch": "git+https://github.com/davidje13/neutrino-patch#semver:^1.0.1"

"The more your tests resemble the way your software is used, the more confidence they can give you. "

You want to write maintainable tests for your React components. As a part of this goal, you want your tests to avoid including implementation details of your components and rather focus on making your tests give you the confidence for which they are intended. As part of this, you want your testbase to be maintainable in the long run so refactors of your components (changes to implementation but not functionality) don't break your tests and slow you and your team down.

We try to only expose methods and utilities that encourage you to write tests that closely resemble how your web pages are used.

The more your tests resemble the way your software is used, the more confidence they can give you.

Most of the damaging features have to do with encouraging testing implementation details. Primarily, these are shallow rendering, APIs which allow selecting rendered elements by component constructors, and APIs which allow you to get and interact with component instances (and their state/properties) (most of enzyme's wrapper APIs allow this).

VitaMy professional story.

homebrewing

Snapchat says it reaches 28.5 to 30 million 18-24 year old users in the U.S. According to a recent survey of Instagram users, approximately 32 percent of its 1 billion-strong user base is 18-24.

# Resources to be used as redirect destinations.