1,029 Matching Annotations
  1. Last 7 days
    1. Industrial concerns doubtless suffer enormous losses from the employment of persons whose mental ability is not equal to the tasks they are expected to perform. The present methods of trying out new employees, transferring them to simpler and simpler jobs as their inefficiency becomes apparent, is wasteful and to a great extent unnecessary. A cheaper and more satisfactory method would be to employ a psychologist to examine applicants for positions and to weed out the unfit. Any business employing as many as five hundred or a thousand workers, as, for example, a large department store, could save in this way several times the salary of a well-trained psychologist.

      I think this is interesting because they are saying that intelligence testing could be used to determine job positions. I agree that employing a psychologist to examine applications for positions would be beneficial because the employer doesn't have to worry about certain things the psychologist would look for. I agree that using a psychologist to weed people out of decision of employment could be effective because many people are applying, but the employers only want certain people for that job. I think this is relevant to the history of psychology because there are some companies who use people to determine who is deemed fit for the company, and this is what they wanted to start doing so they could find the best employees for that particular job.

  2. Mar 2023
    1. Nonparametric statistics are often preferred to parametric tests when the sample size is small and the data are skewed or contain outliers.
    2. when to use parametric versus nonparametric tests [8,9,10]
    1. https://www.antinet.org/wooden-antinet-waitlist

      2023-03-06: Noting that the list price on this has now dropped to $495 including shipping. He's also closed the wait list, which I'm guessing was set up to both collect email addresses as well as to test market the demand for such a box at his various price points.

  3. Feb 2023
    1. What we ultimately should care about is being able to use our knowledge to produce something new, whatever that may be. To not merely reproduce you must understand the material. And understanding requires application, a hermeneutic principle that particularly Gadamer worked out extensively. If you really want to measure your level of understanding, you should try to apply or explain something to yourself or someone else.
  4. Jan 2023
    1. I've seen a bunch of people sharing this and repeating the conclusion: that the success is because the CEO loves books t/f you need passionate leaders and... while I think that's true, I don't think that's the conclusion to draw here. The winning strategy wasn't love, it was delegation and local, on the ground, knowledge.

      This win comes from a leader who acknowledges people in the stores know their communities and can see and react faster to sales trends in store... <br /> —Aram Zucker-Scharff (@Chronotope@indieweb.social) https://indieweb.social/@Chronotope/109597430733908319 Dec 29, 2022, 06:27 · Mastodon for Android

      Also heavily at play here in their decentralization of control is regression toward the mean (Galton, 1886) by spreading out buying decisions over a more diverse group which is more likely to reflect the buying population than one or two corporate buyers whose individual bad decisions can destroy a company.

      How is one to balance these sorts of decisions at the center of a company? What role do examples of tastemakers and creatives have in spaces like fashion for this? How about the control exerted by Steve Jobs at Apple in shaping the purchasing decisions of the users vis-a-vis auteur theory? (Or more broadly, how does one retain the idea of a central vision or voice with the creative or business inputs of dozens, hundreds, or thousands of others?)

      How can you balance the regression to the mean with potentially cutting edge internal ideas which may give the company a more competitive edge versus the mean?

  5. Dec 2022
    1. Let’s say, you’ve set up the list-unsubscribe header to you email campaign. Check out whether it works by sending an email to a test inbox. For Gmail, you’ll see the unsubscribe option in the header right next to the sender name
  6. Nov 2022
    1. I've developed additional perspective on this issue - I have DNS settings in my hosts file that are what resolve the visits to localhost, but also preserve the subdomain in the request (this latter point is important because Rails path helpers care which subdomain is being requested) To sum up the scope of the problem as it stands now - I need a way within Heroku/Capybara system tests to both route requests to localhost, but also maintain the subdomain information of the request. I've been able to accomplish one or the other, but haven't found a configuration that provides both yet.
    1. Honestly, at this point, I don't even know what tools I'm using, and which is responsible for what feature. Diving into the code of capybara and cucumber yields hundreds of lines of metaprogramming magic that somehow accretes into a testing framework. It's really making me loathe TDD despite my previous youthful enthusiasm.

      opinion: too much metaprogramming magic

      I'm not so sure it's "too much" though... Any framework or large software project is going to feel that way to a newcomer looking at the code, due to the number of layers of abstractions, etc. that eventually were added/needed by the maintainers to make it maintainable, decoupled, etc.

    1. module InjectSession include Warden::Test::Helpers def inject_session(hash) Warden.on_next_request do |proxy| hash.each do |key, value| proxy.raw_session[key] = value end end end end
    1. the functional core, imperative shell pattern

      Link to video on "Boundaries" doesn't go into depth on the functional core, imperative shell pattern. However, this one does: https://www.destroyallsoftware.com/screencasts/catalog/functional-core-imperative-shell

    2. For new code, it’s usually a good idea to design the code so that it’s easy to test with “real” objects, rather than stubs or mocks.
    3. We keep our functional tests separate from our unit tests, in the tests/functional directory. Because these are slow to run, we will usually write one or two functional tests to check a new feature works in the common case, and unit tests for all the other cases.

      Keep functional & unit tests separate. Functional for common cases, unit for all others.

    4. To run the backend test suite only call tox directly

      Probably means, "Call tox directly if you only want to run the backend test suite."

    1. How to Turn Obsidian Into a Personal Kanban Organizer

      Checking if Hypothesis works on Android via Brave mobile browser. Here's some LaTex being tested \(A \cup B\)

  7. Oct 2022
    1. strange images with junk and light

      another test annotation

    2. create something weird

      testing hypothesis annotations

  8. Sep 2022
  9. Aug 2022
    1. ReconfigBehSci. (2021, November 26). Parts of Germany seem to have potentially introduced requirements that cannot practically be met as testing capacity is proving insufficient—A dangerous moment for rule compliance Nadelöhr Corona-Tests: “Es ist Wahnsinn” via @sz https://t.co/meLS79RTCw [Tweet]. @SciBeh. https://twitter.com/SciBeh/status/1464287412289511432

  10. Jul 2022
    1. It really slows down your test suite accessing the disk.So yes, in principle it slows down your tests. There is a "school of testing" where developer should isolate the layer responsible for retrieving state and just set some state in memory and test functionality (as if Repository pattern). The thing is Rails is a tightly coupled with implementation logic of state retrieval on core level and prefers "school of testing" in which you couple logic with state retrial to some degree.Good example of this is how models are tested in Rails. You could just build entire test suite calling `FactoryBot.build` and never ever use `FactoryBot.create` and stub method all around and your tests will be lighting fast (like 5s to run your entire test suite). This is highly unproductive to achieve and I failed many times trying to achieve that because I was spending more time maintaining my tests then writing something productive for business.Or you can took more pragmatic route and save database record where is too difficult to just 'build' the factory (e.g. Controller tests, association tests etc)Same I would say for saving the file to the Disk. Yes you are right You could just "not save the file to disk" and save few milliseconds. But at the same time you will in future stumble upon scenarios where your tests are not passing because the file is not there (e.g. file processing validations) Is it really worth it ? I never worked on a project where saving file to a disk would slow down tests significantly enough that would be an issue (and I work for company where core business is related to file uploading) Especially now that we have SSD drives in every laptop/server it's blazing fast so at best you would save 1 seconds for entire test suite (given you call FactoryBot traits to set/store file where it make sense. Not when every time you build an object.)
    1. Điểm đo ở xã Hải Bối, huyện Đông Anh ghi nhận lượng mưa lớn với gần 250 mm. Tại nội thành, quận Bắc Từ Liêm mưa lớn nhất 240 mm, Cầu Giấy gần 140 mm, các quận Nam Từ Liêm, Bắc Từ Liêm, Hà Đông trên 100 mm.

      Đoạn này là sao ấy nhỉ

  11. Jun 2022
    1. Black Box testing: Software on the rack

      Black Box testing: Software on the rack

      Black Box testing is defined as a testing technique in which the functionality of an application is tested without looking at the internal code structure, implementation details and knowledge of internal paths of the software. This type of testing is completely based on software requirements and specifications.

    1. When a few of his friends became interested in thetopic, he took eight minutes to progressively summarize the bestexcerpts before sharing the summarized article with them. The timethat he had spent reading and understanding a complex subject paidoff in time savings for his friends, while also giving them a newinterest to connect over.

      To test one's own understanding of a topic one has read about and studied, it can be useful to discuss it or describe one's understanding to friends or colleagues in conversations. This will help you discover where the holes are based on the person's understanding and comprehension of what you've said. Can you fill in all the holes where they have questions? Are their questions your new questions which have exposed holes that need to be filled in your understanding or in the space itself.

      I do this regularly in conversations with people. It makes the topics of conversation more varied and interesting and helps out your thinking at the same time. In particular I've been doing this method in Dan Allosso's book club. It's almost like trying on a new idea the way one might try on a piece of clothing to see how it fits or how one likes it for potential purchase. If an idea "fits" then continue refining it and add it to your knowledge base. These conversations also help to better link ideas in my thought space to those of what we're reading. (I wonder if others are doing these same patterns, Dan seems to, but I don't have as good a grasp on this with other participants).

      Link to :<br /> - Ahren's idea of writing to expose understanding<br /> - Feynman technique<br /> - Socratic method (this is sort of side or tangential method to this) <- define this better/refine

    1. 7 Software Test Principles

      It is important that you achieve optimal test results with software testing without deviating from the test goal. But how do you determine whether you are following the right test strategy? For this you have to follow a number of basic principles.

  12. May 2022
    1. Some Test Scenarios: * Single or multi-browser testing * Downloading an app to the desktop * Installing browser extensions

  13. Apr 2022
    1. Individuals who harbor germline pathogenic variants in DICER1 (MIM #601200) have an increased risk for a variety of benign and malignant tumors.


    1. The issue that had roiled the grown-ups in his life seemed to have had no effect on him at all.

      I wonder if that suggests the tests matter less, or more?

    2. A 95 percent opt-out rate was a resounding success. It rivaled election results in Turkmenistan.

      Wow. That's an incredibly long reach to make an incendiary point.

    1. Ashish K. Jha, MD, MPH. (2020, October 27). President keeps saying we have more cases because we are testing more This is not true But wait, how do we know? Doesn’t more testing lead to identifying more cases? Actually, it does So we look at other data to know if its just about testing or underlying infections Thread [Tweet]. @ashishkjha. https://twitter.com/ashishkjha/status/1321118890513080322

    1. Dr Nisreen Alwan 🌻. (2021, March 14). Exactly a year ago we wrote this letter in the Times. We were gobsmacked! We just didn’t understand what the government was basing all its decisions on including stopping testing and the herd immunity by natural infection stuff. We wanted to see the evidence backing them. [Tweet]. @Dr2NisreenAlwan. https://twitter.com/Dr2NisreenAlwan/status/1371168531669258242

    1. Denise Dewald, MD 🗽. (2021, August 12). Here are some modeling predictions for the delta variant from COVSIM (group at North Carolina State): PLEASE CHECK THIS OUT - RESOURCES TO SHARE WITH YOUR SCHOOL DISTRICT School-level COVID-19 Modeling Results for North Carolina for #DeltaVariant https://t.co/zU5hB9bKlY [Tweet]. @denise_dewald. https://twitter.com/denise_dewald/status/1425626289399009288

    1. When setting up SAML SSO in your organization, you can test your implementation without affecting your organization members by leaving Require SAML SSO authentication for all members of the organization name organization unchecked.
    1. Manual testing is a type of software test in which testers manually carry out test cases without using automation tools. Testers are actually behind the screen of the application, carry out test cases and see what the result is.

      What is manual testing?

      Manual testing is a type of software test in which testers manually carry out test cases without using automation tools. Testers are actually behind the screen of the application, carry out test cases and see what the result is.

  14. Mar 2022
    1. A test case is a series of actions that are performed to determine a specific function or functionality of your application. Test scenarios are rather vague and include a wide range of variables. However, testing is all about being very specific. That is why we need elaborate test cases.

      Test cases, examples and Best Practices A test case is a series of actions that are performed to determine a specific function or functionality of your application. Test scenarios are rather vague and include a wide range of variables. However, testing is all about being very specific. That is why we need elaborate test cases.

    1. Capybara can get us part of the way there. It allows us to work with an API rather than manipulating the HTML directly, but what it provides isn't an application specific API. It gives us low-level API methods like find, fill_in, and click_button, but it doesn't provide us with high-level methods to do things like "sign in to the app" or "click the Dashboard item in the navigation bar".
    2. A page object is a data structure that provides an interface to your web application for the purposes of test automation. For example, it could represent a single HTML page, or perhaps even a fragment of HTML on a page.
    3. A page object wraps an HTML page, or fragment, with an application-specific API, allowing you to manipulate page elements without digging around in the HTML.
    1. this gem promotes writing tests for data migrations providing a way allows to write code that migrates data in separate methods.
    2. having the code migrates data separately covered by proper tests eliminates those pesky situations with outdated migrations or corrupted data.
  15. Feb 2022
    1. STLC - Software Testing Life Cycle

      Software Testing Life Cycle (STLC) is defined as a set of activities performed to perform software testing. The Software Testing Life Cycle refers to a testing process with specific steps that must be performed in a specific order to ensure that quality objectives are met.

    1. Because CENS was an academic research lab, faculty members held a large amount of power to decide which projects students pursued and what issues students faced during design, testing, and implem

      CENS seems like it takes its job seriously. Like I said in my other annotation for week 5. Just because data scientists are trying to root out bias in all forms doesn't mean it is always effective or that what is effective can't be improved.

    1. Mahan Ghafari, ماهان غفاری. (2022, February 1). After the daily covid-19 cases in Iran dropped to record-low numbers last month, it is now back in full swing due to omicron! Map on the left (mostly coloured in blue) shows the situation in late december and the one on the right is from 2 days ago (many in amber or red). 1/ https://t.co/vgpwuiymbl [Tweet]. @Mahan_Ghafari. https://twitter.com/Mahan_Ghafari/status/1488481042847698946