14 Matching Annotations
  1. Dec 2019
    1. Before each election, I have traditionally written up an analysis of the California ballot measures and send it to my friends. It's not always obvious what the "real" agenda is on each one, and even with clear purposes there are often competing interests at play. These writings are the result of my own analysis, which comes from a libertarian perspective, and I'm not knowingly affiliated with any party behind any ballot measure. I believe that mere lists of "vote yes" or "vote no" are not very helpful except for sheep: it's important to know why one is urged to vote in any given direction. I would rather you vote against my position because you had an opposing view than vote with my position because you flipped a coin.
  2. 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).
  3. Oct 2019
  4. Aug 2019
  5. Dec 2015
    1. RAJ: Paul, you are suffering from your “should” system. You are experiencing how difficult it is to lay down conceptualized processes and theories. I will not leave my position that this conceptual thinking relates in no way to what is Actually going on—which is the infinitude of your Being unfolding Itself perfectly, properly, and nondestructively—except of course, in terms of these concepts which are binding you. They will be destroyed. They no longer serve to move you to a new base. As you are discovering, the concepts are actually impeding your growth. You must lay them down. The growth will occur. The growth is occurring. This is why you feel shoved into the corner right along with the concepts. Figuratively speaking, this is why you feel that you are going to be blown up in the blowing up of your concepts.

      Paul is suffering because he thinks things should be different than what they are.

      Raj says that "should" stance illustrates how difficult it is to lay down concepts and theories. This Links directly to ACIM Lesson 189, Simply do this...

      Raj says what's Actually going on is the "infinitude of your Being unfolding itself perfectly, properly, and nondestructively"...

      Paul can't see this because of the concepts that bind him.