Professional musicians, concert pianists get to know this instrument deeply, intimately. And through it, they're able to create with sound in a way that just dazzles us, and challenges us, and deepens us. But if you were to look into the mind of a concert pianist, and you used all the modern ways of imaging it, an interesting thing that you would see 00:11:27 is how much of their brain is actually dedicated to this instrument. The ability to coordinate ten fingers. The ability to work the pedal. The feeling of the sound. The understanding of music theory. All these things are represented as different patterns and structures in the brain. And now that you have that thought in your mind, recognize that this beautiful pattern and structure of thought in the brain 00:11:52 was not possible even just a couple hundred years ago. Because the piano was not invented until the year 1700. This beautiful pattern of thought in the brain didn't exist 5,000 years ago. And in this way, the skill of the piano, the relationship to the piano, the beauty that comes from it was not a thinkable thought until very, very recently in human history. 00:12:17 And the invention of the piano itself was not an independent thought. It required a depth of mechanical engineering. It required the history of stringed instruments. It required so many patterns and structures of thought that led to the possibility of its invention and then the possibility of the mastery of its play. And it leads me to a concept I'd like to share with you guys, which I call "The Palette of Being." 00:12:44 Because all of us are born into this life having available to us the experiences of humanity that has come so far. We typically are only able to paint with the patterns of thoughts and the ways of being that existed before. So if the piano and the way of playing it is a way of being, this is a way of being that didn't exist for people 5,000 years ago. 00:13:10 It was a color in the Palette of Being that you couldn't paint with. Nowadays if you are born, you can actually learn the skill; you can learn to be a computer scientist, another color that was not available just a couple hundred years ago. And our lives are really beautiful for the following reason. We're born into this life. We have the ability to go make this unique painting with the colors of being that are around us at the point of our birth. 00:13:36 But in the process of life, we also have the unique opportunity to create a new color. And that might come from the invention of a new thing. A self-driving car. A piano. A computer. It might come from the way that you express yourself as a human being. It might come from a piece of artwork that you create. Each one of these ways of being, these things that we put out into the world 00:14:01 through the creative process of mixing together all the other things that existed at the point that we were born, allow us to expand the Palette of Being for all of society after us. And this leads me to a very simple way to go frame everything that we've talked about today. Because I think a lot of us understand that we exist in this kind of the marvelous universe, 00:14:30 but we think about this universe as we're this tiny, unimportant thing, there's this massive physical universe, and inside of it, there's the biosphere, and inside of that, that's society, and inside of us, we're just one person out of seven billion people, and how can we matter? And we think about this as like a container relationship, where all the goodness comes from the outside to the inside, and there's nothing really special about us. 00:14:56 But the Palette of Being says the opposite. It says that the way that we are in our lives, the way that we affect our friends and our family, begin to change the way that they are able to paint in the future, begins to change the way that communities then affect society, the way that society could then affect its relationship to the biosphere, and the way that the biosphere could then affect the physical planet 00:15:21 and the universe itself. And if it's a possible thing for cyanobacteria to completely transform the physical environment of our planet, it is absolutely a possible thing for us to do the same thing. And it leads to a really important question for the way that we're going to do that, the manner in which we're going to do that. Because we've been given this amazing gift of consciousness.

That's a picture of it in the background. And this organism has the special trick that we call "photosynthesis," the ability to go take energy from the sun and transform carbon dioxide into oxygen. And over the course of billions of years, so starting from two and a half billion years ago, little by little these bacteria spread across the planet 00:07:08 and converted all that carbon dioxide in the air into the oxygen that we now have. And it was a very slow process. First, they had to saturate the seas, then they had to saturate the oxygen that the earth would absorb, and only then, finally, could oxygen begin to build up in the atmosphere. So you see, just after about 900 million years ago, oxygen starts to build up in the atmosphere. And about 600 million years ago, something really amazing happens. 00:07:35 The ozone layer forms from the oxygen that has been released in the atmosphere. And it sounds like a small deal, like we talked about the ozone a couple decades ago, but it actually turns out that before the ozone layer existed, earth was not really able to sustain complex, multicellular life. We had single-celled organisms, we had a couple of simple, multicellular organisms, but we didn't really have anything like you or me. 00:07:59 And shortly after the ozone layer came into place, the earth was able to sustain complex multicellular life. There was a Cambrian explosion of life in the seas. And the first plants got onto land. In fact, there was actually no life on land ahead of that. Another way to see this is, this is kind of a chart of pretty much most of the animals that you guys are familiar with. 00:08:24 And right at the bottom in time is the formation of the ozone layer. Like nothing that you are familiar with today could exist without the contributions of these tiny organisms over those billions of years. And where are they now? Well actually, they never really left us. The direct descendants of the cyanobacteria were eventually captured by plants. And they're now called chloroplasts. 00:08:49 So this is a zoom-in of a plant leaf - and we probably ate some of these guys today - where tons of little chloroplasts are still trapped - contributing photosynthesis and making energy for the plants that continue to be the other half of our lungs on earth. And in this way, our breaths are very deeply united. Every out-breath is mirrored by the in-breath of a plant,

today I'm here to describe that everything really is connected, 00:02:02 and not in some abstract, esoteric way but in a very concrete, direct, understandable way. And I am going to do that with three different stories: a story of the heart, a story of the breath, and a story of the mind.

Fundamental features of human psychology can constrain the perceived personal relevance and importance of climate change, limiting both action and internalization of the problem. Cognitive shortcuts developed over millennia make us ill-suited in many ways to perceiving and responding to climate change (152), including a tendency to place less emphasis on time-delayed and physically remote risks and to selectively downplay information that is at odds with our identity or worldview (153). Risk perception relies on intuition and direct perceptual signals (e.g., an immediate, tangible threat), whereas for most high-emitting households in the Global North, climate change does not present itself in these terms, except in the case of local experiences of extreme weather events. Where strong concern does exist, this tends to be linked to care for others (154) combined with knowledge about the causes and possible consequences of climate change (155).

The next day, I assumed we would begin our quest to find signs of hyperobjects in and around the city of Houston

I was speaking in Iowa, and I was asked, “How do you talk to people in Iowa about polar bears?” I said, “You don’t; you talk to them about corn.” If we begin a conversation with someone with something we already agree on, then the subtext is: “You care about this, and I care too. We have this in common.”

Fundamental features of human psychology can constrain the perceived personal relevance andimportance of climate change, limiting both action and internalization of the problem. Cognitiveshortcuts developed over millennia make us ill-suited in many ways to perceiving and respondingto climate change (152),including a tendency to place less emphasis on time-delayed and physicallyremote risks and to selectively downplay information that is at odds with our identity or worldview(153). Risk perception relies on intuition and direct perceptual signals (e.g., an immediate, tangiblethreat), whereas for most high-emitting households in the Global North, climate change does notpresent itself in these terms, except in the case of local experiences of extreme weather events.

With the aid of the concept of opposing pairs of magnetic poles, we can clearly contribute in a significant way to our expression and understanding of basic relationships in the overall magnetic field. We are proposing to look at soma and significance in a similar way. That is to say, we regard them as two aspects introduced at an arbitrary conceptual cut in the flow of the field of reality as a whole. These aspects are distinguished only in thought, but this distinction helps us to express and understand the whole flow of reality.

The Art of Gathering: How We Meet and Why It Matters

“There is LeBron James, but it’s not LeBron James. It’s a cartoon version of him.”

The classic SPA example is a to-do list. But, you know what? I don't like to-do lists. They make me think about all the things I have to do, many of which I don't want to do.So why don't we make a To-Don't List app? That way we can list all the things we're not going to do. Ever.

3. The no-keyword-arguments syntax (**nil) is introduced You can use **nil in a method definition to explicitly mark the method accepts no keyword arguments. Calling such methods with keyword arguments will result in an ArgumentError. (This is actually a new feature, not an incompatibility)

This is useful to make it explicit that the method does not accept keyword arguments. Otherwise, the keywords are absorbed in the rest argument in the above example.

You need to explicitly delegate keyword arguments. def foo(*args, **kwargs, &block) target(*args, **kwargs, &block) end

foo({}, **{}) #=> Ruby 2.7: [{}] (You can pass {} by explicitly passing "no" keywords)

In the end this plugin is a piece of software that I wrote and I'm just doing what I think is reasonable to make our community more inclusive.

He was telling me it was 3,500, but the landlord was keeping 2,500 and giving him 1,000 of it. And I had found out, because the own landlord lady told me, and I had to move and I had to lose my job.

Prettier intentionally doesn’t support any kind of global configuration. This is to make sure that when a project is copied to another computer, Prettier’s behavior stays the same. Otherwise, Prettier wouldn’t be able to guarantee that everybody in a team gets the same consistent results.

Explicit types for function return values and arguments makes it clear to any calling code what is the module boundary's input and output.

Some people, regardless of their experience level are horrible as teachers. A school teacher gets asked the same question every year. Every year they answer them, even if it seems redundant, and the answers are simple to THEM. Teaching requires patience and the acceptance of being asked "dumb questions" repeatedly. If they cannot handle that, then they should simply not teach or pretend to be a teacher.

If your python3 executable is named "python" instead of "python3" (this particularly appears to affect a number of Windows users), then you'll also need to modify the first line of git-filter-repo to replace "python3" with "python".

--tag-rename '':'my-module-' (the single quotes are unnecessary, but make it clearer to a human that we are replacing the empty string as a prefix with my-module-)

They're less likely to go into the "Promotions" tab in Gmail (used by ~16% of all email users), for the same reasons above. From my testing, the plain emails typically end up in the Updates tab and some times even in the primary tab. Of course, the text in the email also affects this.

You can use a free spam checker to validate this by testing plain and designed emails.

These example are for Rails applications, but there is no dependency on Rails for using this gem. Most of the examples are applicable to any Ruby application.

Explicit affordances are obvious, perceptual features of an item that clue you in on how it is to be used. With explicit affordances, physical appearance and any accompanying language or text inform the user of how an object is to be used.

This isn't really a downside to React; one of React's strengths is that it lets you control so much and slot React into your environment

I like this approach more because I can scan the code that renders the Box component and easily spot that it takes two children. If the Box took any props, they'd be within the opening <Box> tag, and they would be distinct from any children props.

Small modules are extremely versatile and easy to compose together in an app with any number of other modules that suit your needs.

Occasionally, like with search engines, #2 occurs because the incumbents gain massive economies of scale (classic Microeconomics), where by virtue of their being large, the cost to produce each incremental good or service at scale becomes much lower.

It can also be included as individual modules, i.e. Hashie::Extensions::MethodReader, Hashie::Extensions::MethodWriter and Hashie::Extensions::MethodQuery.

the explicit modelling has one massive advantage: all possible outcomes of the nested activity are visible and have to be connected in the outer diagram

To understand this helper, you should understand that every step invocation calls Output() for you behind the scenes. The following DSL use is identical to the one [above]. class Execute < Trailblazer::Activity::Railway step :find_provider, Output(Trailblazer::Activity::Left, :failure) => Track(:failure), Output(Trailblazer::Activity::Right, :success) => Track(:success)

Feel free to pick and choose what you need for your applications.

Because the Berne Convention in most countries by default grants copyright holders monopolistic control over their creations, copyright content must be explicitly declared free, usually by the referencing or inclusion of licensing statements from within the work.

The bare bones operation without any Trailblazery is implemented in the trailblazer-operation gem and can be used without our stack.

While Trailblazer offers you abstraction layers for all aspects of Ruby On Rails, it does not missionize you. Wherever you want, you may fall back to the "Rails Way" with fat models, monolithic controllers, global helpers, etc. This is not a bad thing, but allows you to step-wise introduce Trailblazer's encapsulation in your app without having to rewrite it.

Only use what you like.

you can pick which layers you want. Trailblazer doesn't impose technical implementations

Can't have a steam library without MMX.

I feel like I should've paid more for this masterpiece.

The Java packages contain a lot of great code. But there are also parts of that code I'm sure the authors are embarrassed to admit they wrote.

We got this email from Parabo, the print shop app, and smiled. Instead of the very standard “Please confirm subscription” header text, we were greeted with a funny, whimsical hello that’s totally in their brand voice. “We really want you to want us” is a clever way to break up the usual mundane greeting, and, guess what? It totally reaffirmed why we thought we wanted to sign up for their emails in the first place.

Instead of trying to educate everyone on the complexities of copyright law, we’d rather make our intentions clear with this simple statement:

this second approach, while more verbose, sort of spells out better where things are coming from. (I like it, in other words.)

I don't think this is what really matters at the end, since whatever is the implementation the goal should be to provide a library that people actually like to use.

The Thirteen Sources of Well-Being:More positive emotionsFewer negative emotionsLife satisfactionVitalityEnvironmental masteryPositive relationshipsSelf-acceptanceMasteryAutonomyPersonal growthEngagement in lifePurpose and meaning in lifeTranscendent experiences

This one gets the SEO, so I hope you're successful @raythurnevoid.

This decorators proposal is based on a common model where each decorator affects just one syntactic element--either a field, or a method, or a getter, or setter, or a class. It is immediately visible what is being decorated.

There are several built-in modules — math, color, string, list, map, selector, and meta — which have to be imported explicitly in a file before they are used:

In brief, @import is being replaced with more explicit @use and @forward rules. Over the next few years Sass @import will be deprecated, and then removed.

There's an issue #3368 for describing better what triggers reactive updates, as I do think there is some stuff we could be more explicit about

It will not re-run your component’s code on update unless explicitly told to do so, using the $: operator.

Scholars like Annette Gordon-Reed and Woody Holton have given us a deeper understanding of the ways in which leaders like Thomas Jefferson committed to new ideas of freedom even as they continued to be deeply committed to slavery.

I couldn't land on how I wanted to box primitives. Should I use a getter/setter, or function form like Knockout, or explicit get/set like MobX? These were all ugly.

In my opinion, because Webpack was one of the first bundlers, is heavily packed with features, and has to support swathes of legacy code and legacy module systems, it can make configuring Webpack cumbersome and challenging to use. Over the years, I’ve written package managers, compilers, and bundlers, and I still find configuring Webpack to be messy and unintuitive.

Explicit interfaces are preferable, even if it places greater demand on library authors to design both their components and their style interfaces with these things in mind.

Web developers are well aware of the mess you can get into with global CSS, and the action of writing <Child class="foo"/> and <div class={_class}>` (or similar) in the child component is an explicit indication that, while taking advantage of all the greatness of style encapsulation by default, in this case you have decided that you want a very specific and controlled "leak", of one class, from one component instance to one component instance.

Besides, it's probably better for component authors to be explicit about whether or not their component maps to a specific runtime element.

There are tools in Svelte that break this expectation to a degree, but they are a bit annoying to use, which makes it an active decision on the part of the developer. The API hints at the way we want you to do things because we feel that this will give the better experience.

If you copy an entire article from this site and republish it on your own site like you wrote it, that’s a little uncool. I won’t be mad at you for stealing, I just think you’re better than that and want to see you do better. I’m not going to come after you though. I’d rather play ball with my dog. The only time I’ll be mad at you is if you go out of your way to try and hurt me somehow. And again I probably won’t even be mad, just sad. Unless I’m having a bad day too, in which case I apologize in advance for my snarky replies.

Can't upvote this enough. It is highly irritating to see language destroyed (and we wonder why kids bastardize the language..).

It’s so much easier to be a critic than a celebrator. Always remember there is a human being on the other end of every exchange and behind every cultural artifact being critiqued.

Explicit Form (where the purpose of the sign-up mechanism is unequivocal). So for example, in a scenario where your site has a pop-up window that invites users to sign up to your newsletter using a clear phrase such as: “Subscribe to our newsletter for access to discount vouchers and product updates!“, the affirmative action that the user performs by typing in their email address would be considered valid consent.

Generally, these laws apply to any service targeting residents of the region, which effectively means that they may apply to your business whether it’s located in the region or not.

I originally did not use this approach because many pages that require translation are behind authentication that cannot/should not be run through these proxies.

Generally, such legislations apply to any service targeting residents of the region, which effectively means that they may apply to your business whether it’s located in the region or not

These rules usually apply to any company selling to EU residents but may vary for international sellers on a case-by-case basis. It is worth noting, however, that in recent cases US courts have chosen to uphold the applicable EU law.