27 Matching Annotations
  1. Nov 2020
  2. Oct 2020
    1. light microscopes

      This scientific instrument is used to visually depict the details of an object through the use of a magnified image shown by a series of glass lenses. These glass lenses focus the light shining down onto the object and then the lenses magnify the object for better depiction. The lenses can rotate out to for more/less magnification, and the floor platform the object is held onto can also be lowered/risen for a better focus as well.

  3. Sep 2020
  4. Jul 2020
    1. It would be nice if the tests weren't so implementation specific, but rather tested the essence of the functionality. I tried to make them less brittle but failed. To that end, re-writing all the tests in rspec would be (IMHO) a brilliant improvement and pave the way for better tests in the future and more flexibility in implementation.
  5. Apr 2020
    1. Running the same code in the browser and on the server in order to avoid code duplication is a very different problem. It is simply a matter of good development practices to avoid code duplication. This however is not limited to isomorphic applications. A utility library such as Lodash is “universal”, but has nothing to do with isomorphism. Sharing code between environments does not give you an isomorphic application. What we’re referring to with Universal JavaScript is simply the fact that it is JavaScript code which is environment agnostic. It can run anywhere. In fact most JavaScript code will run fine on any JavaScript platform.
    2. Having the server render the HTML on first page load is the functional part, the thing that provides for a better user experience. The technical part is where we use the same code in both environments, which no user ever asked for, but makes a developer’s life easier (at least in theory).
    1. Devise-Two-Factor only worries about the backend, leaving the details of the integration up to you. This means that you're responsible for building the UI that drives the gem. While there is an example Rails application included in the gem, it is important to remember that this gem is intentionally very open-ended, and you should build a user experience which fits your individual application.
  6. Mar 2020
  7. Nov 2019
    1. it doesn't even render in-file components. For example, the <Fade /> component we have above is an implementation detail of the <HiddenMessage /> component, but because we're shallow rendering <Fade /> isn't rendered so changes to that component could break our application but not our test. That's a major issue in my mind and is evidence to me that we're testing implementation details.
    2. The reason this kind of test fails those considerations is because it's testing irrelevant implementation details. The user doesn't care one bit what things are called. In fact, that test doesn't even verify that the message is hidden properly when the show state is false or shown when the show state is true. So not only does the test not do a great job keeping us safe from breakages, it's also flakey and doesn't actually test the reason the component exists in the first place.
    3. I could rename toggle to handleButtonClick (and update the corresponding onClick reference). My test breaks despite this being a refactor.
    4. I could mistakenly set onClick of the button to this.tgogle instead of this.toggle. My test continues to work, but my component is broken.
    5. Will this test break when there's a mistake that would break the component in production?Will this test continue to work when there's a fully backward compatible refactor of the component?
    1. Why is testing implementation details bad?There are two distinct reasons that it's important to avoid testing implementation details. Tests which test implementation details:Can break when you refactor application code. False negativesMay not fail when you break application code. False positives
    1. But far too often, I see tests which are testing implementation details (read this before continuing if you haven't already). When you do this, you introduce a third user. The developer user and the end user are really all that matters for this component. So long as it serves those two, then it has a reason to exist. And when you're maintaining the component you need to keep those two users in mind to make sure that if you break the contract with them, you do something to handle that change.But as soon as you start testing things which your developer user and end user don't know or care about (implementation details), you add a third testing user, you're now having to keep that third user in your head and make sure you account for changes that affect the testing user as well.
    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.
  8. Sep 2019
  9. span2204.commons.gc.cuny.edu span2204.commons.gc.cuny.edu
    1. Thus, even though these numbers turned out to be exaggerated, the authority of their source—the INS—meant that they entered public discourse as a symbol of alarm.29For example, the December 1974 cover of the American Legion Magazinedepicted the United States being overrun by “illegal aliens” (Figure 1.1). Most of the cartoon people in the image are Mexicans storming, en masse, across the U.S.-Mexico border, breaking down a sign that reads “usa border” and another one reading “keep out.” Other immigrants are landing by boats along theEast Coast, flying in and swimming from the Caribbean, parachuting acrossthe Canadian border, and all of them are converging upon, and inundat-ing, the nation’s institutions, most notably welfare, education, housing, jobs, and medical care. Such images were to become more frequent in the nation’s magazines over the next three decades, contributing to an increasingly alarmist d

      I feel that cartoons (in magazines/newspapers/etc) always tend to implicate some type of "joke" because it is illustraited in a way that should just be a slap in the writst just because it is a drawing and it is "funny"because it is a cartoon. But there has been a a lot of cartoons HYSTORICALLY publicly published that no doubt has racism stamped all over it. No difference with this cartoon there is stereotypes of Mexicans with sombreros and almost racing to these facilities. I also think of the illustraitor and what type of person is he and what his/her intensions were to be using effort and tallent on something so RACIST.

  10. May 2019
    1. Murine macrophage cell line J774A.1 (ATCC no. TIB-67) was maintained in phenol red free DMEM supplemented with 10% heat inactivated (45 min at 65°C) foetal bovine serum at 37°C in 5% C02 and 95% air. The cultures were sub-cultured every three days or at the attainment of 80 % confluency.
  11. Nov 2017
  12. Oct 2017
  13. Nov 2016
    1. Les fouilles se poursuivent pendant une décennie suivant la découverte, sous le regard des autorités jordaniennes mais nous avons peu de détails sur le déroulement de celles-ci.

      Est-ce qu’on sait pourquoi nous avons peu de détails sur le déroulement des fouilles? Était-ce en lien avec un climat politique particulier, ou une pratique de l'archéologie généralement négligée à cette époque, dans cette région?

  14. Feb 2016
    1. Recount stories, including fables, folktales, and myths from diverse cultures; determine the central message, lesson, or moral and explain how it is conveyed through key details in the text

      Students must read a wide variety of fiction story types, understand the moral, and explain what key details help identify it. I think stories about the greek gods would be fun and exciting for kids, possibly Hercules as a book and movie follow up.

  15. Oct 2015
    1. full loss function as coming from a Gaussian prior over the weight matrix WW, where instead of MLE we are performing the Maximum a posteriori (MAP) estimation. We mention these interpretations to help your intuitions, but the full details of this derivation are beyond the scope of this class.

      Can anyone provide resources where I can find this derivation? In particular, the derivation for the regularization term \(R(W)\) coming from a Gaussian prior on \(W\).

  16. Jan 2014
    1. I regret that the documentation does not focus on what is most relevant; by focusing on a largely irrelevant implementation detail, we enlarge the importance of that implementation detail and obscure the importance of what makes a value type semantically useful. I dearly wish that all those articles explaining what “the stack” is would instead spend time explaining what exactly “copied by value” means and how misunderstanding or misusing “copy by value” can cause bugs.

      Documentation should focus on semantically useful descriptions; another accompanying document (or annotation) can provide relevant implementation details upon request, but that deeper level of detail should be left out by default to avoid enlarging the importance of less relevant things.