59 Matching Annotations
  1. Sep 2021
  2. Aug 2021
    1. 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

      Important

  3. Jul 2021
    1. sinful

      This is another word that Miss Clack used a lots in her narrative.

    2. devout

      The word "devout" came out a few thing from Miss Clack's narrative. I assume she is a devout Christian?

    3. alas!

      This is one of words that Miss Clack will use, but Betteredge won't use. However, this word also reveals some personality of Miss Clack, by definition, alas means: "an expression of grief, pity, or concern." By this we can assume Miss Clack might be a sentimental person

  4. Jun 2021
  5. Apr 2021
    1. 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. 
    1. 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.
  6. Mar 2021
    1. Software that is not currently being used gradually becomes unusable as the remainder of the application changes.
    2. 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.
    1. 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.
    1. 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.
    2. There’s no need to test controllers, models, service objects, etc. in isolation
    3. 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.
  7. Feb 2021
    1. 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.
    1. Operations don't know about HTTP or the environment. You could use an operation in Rails, Hanami, or Roda, it wouldn't know.
  8. Dec 2020
  9. Nov 2020
    1. Many linguists believe that the natural language a person speaks affects how they think. Does the same concept apply to computer languages?
  10. Oct 2020
    1. All validators can be used independently. Inspried by functional programming paradigm, all built in validators are just functions.

      I'm glad you can use it independently like:

      FormValidation.validators.creditCard().validate({
      

      because sometimes you don't have a formElement available like in their "main" (?) API examples:

      FormValidation.formValidation(formElement
      
    1. 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.
  11. Sep 2020
    1. Passing the class prop to the root dom element is already a wide spread practice
    2. 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.
    3. 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
    1. 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.
    2. 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.
    1. 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?
  12. Jul 2020
  13. Mar 2020
    1. Used By

      I like how they have indexed their core code base so they can show in both directions:

      • which other core functions a function uses
      • which other core functions use this function (references)
  14. Dec 2019
  15. Nov 2019
    1. 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.
    1. The more your tests resemble the way your software is used, the more confidence they can give you.
    2. 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).
  16. Aug 2019
  17. May 2019
    1. homebrewing

      Very grass roots/home brew friendly organization; appeals to sense of independence and optimism; "home grown"

  18. Sep 2018
    1. 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.

      Snapchat reaches around 30 million 18-24 year old users; important ages that are more recently able to vote and take political action. Instagram and snapchat are most popular amongst younger users.

  19. Oct 2016
  20. Aug 2015