we can see more specific changes in the brain through training the Mind than through any drug that you can take more specific changes uh when you take a medication like an an SSRI an anti-depressant or an anti psychotic it's like blasting the brain uh in in its entire uh and so it's a very general effect we can see a much more specific effect with mind training

I actually think that there are physiological mechanisms of hibernation that may be relevant to understanding some of the changes in tukon

he earliest we've been able to get to a case of tukdam is 26 hours after a practitioner has died so we've missed the first full day and there is some reason to believe that that first 24-hour period is is going to be very very important

the body of a practitioner in tukdam does not decompose uh in the same way that a body of a normal person who is not in tukdam does and so uh we've had cases up to 38 days uh inam where the body remains quite preserved uh fresh uh without any smell uh and um with the skin still very pliable and no um Rigamortis

his Holiness um uh his Holiness uh made the request that we investigate tokam and I believe that one of uh his interests his Holiness his interest in studying took down is because this represents a real challenge to Western science because uh uh the suggestion in the traditional Tibetan texts is that there is a subtle quality of awareness that is still present even after the conventional Western definition of death after the heart has stopped beating after the breathing has stopped there they're said to be uh this subtle quality of awareness uh this clear light stage that is still present

in our work on well-being we have formulated a framework for understanding the key pillars or the key components of well-being

the fourth pillar of well-being we call purpose

research shows that it's not so much about changing the narrative that is important but it is changing our relationship to this narrative so that we can see the narrative for what it is which is really a constellation of thoughts

the third pillar we call Insight

his Holiness reminds us that the seeds of compassion are often in the relationship between a child and his mother excuse me that a mother provides for the child provides kindness and uh care for the child and represents this early seed of compassion

we think of kindness and compassion in a way that's very similar to the way scci other scientists think about language

it confirms something found in the Buddhist tradition uh which is this notion of innate basic goodness that all human beings are born with Buddha nature we all have the seeds of kindness within us and scientific research strongly confirms that this is true

in a recent study with a very large group of six-month-old infants 100% of infants show this preference so it's not just a small statistically significant difference it's huge virtually every infant shows this

the second pillar of well-being we call connection

very famous scientific experiment that was published about 10 years ago now that is um really a critical experiment in this area

the first pillar we call awareness

two great drivers of plasticity or the two great mechanisms of plasticity

all of us are born with a sequence of base pairs that constitute our DNA and for the most part that will not change over the course of your lifetime but what will change is the extent to which any Gene is turned on or turned off

what we have found quite remarkably is that when a person trains their mind their well-being improves and their brain changes uh and not just the brain but many other things in their mind and body also change

he reason why we're so interested in well-being is because we believe that well-being is best regarded as a skill

Most environmental books now are about practical technological innovation or social changes that have to happen. My argument is that’s not going to work. That’s not going to happen. It requires a transformation in our assumptions about the nature of what we are and what the world is. Otherwise, that instrumental and exploitative relation will remain.

“There are a lot of people who mistakenly think intelligibility is the standard. ‘Oh, you knew what I was saying.’ Well, that’s not the standard. That’s a really bottom-of-the-barrel standard,” he says. “People who are concerned with English usage usually want to have their words taken seriously, either as writers or as speakers. And if you don’t use the language very well, then it hard to have people take your ideas seriously. That’s just the reality.”

We define a crisis as a sudden (non-linear) event or series of events that significantly harms, in a relatively short period of time, the wellbeing of a large number of people (Homer-Dixon et al., Reference Homer-Dixon, Walker, Biggs, Crépin, Folke, Lambin, Peterson, Rockström, Scheffer, Steffen and Troell2015).Footnote

Let your operating system handle daemons, respawning and logging while you focus on your application features and users.

It was enclosed in scare quotes, a sort of acknowledgment that the author knew it was non-standard, but was too apt for the purpose to resist. I remember reading it and trying to think of the “real” word that would be employed there, but could not find a satisfactory alternative. Since then, I’ve found myself unable to resist using the word when appropriate, due to its utility!

if you want to age well do something it can be dancing it can be music it can be all sorts swimming 00:56:47 whatever but do something that's the first bit of advice to those who want to make sure that they stay um on top

others argue that it's not an interpreted language and that it's actually a compiled language

Nevertheless, despite the impact of multimedia tools on the improvement of teaching and learning activities, it could be counterproductive if the computer-based tools are not properly designed or the instructional materials are not well composed.

Male orphans were taught to hold a musket as soon as they werephysically able.44

climate change performance index

Introducing relationships between issues will considerably increase the complexity of GitLab. That is not a reason not to do it. But it is a reason for us to be strategic in when we do it, and ensure we have a good design that is scalable and aligns with our other initiatives.

when we're investing in the stock market, we're mostly just hoping that the value of those shares will rise. That money is not actually reaching companies and being used in productive ways. And that's true. We can see it with private equity too.

these people who go out to murder others hug their children in the morning and leave their homes thinking that Exterminating other people will make 00:16:51 them eternally happy and they can finally live as they please yeah I mean that's what they think they don't go out thinking you 00:17:04 know I'm going to harm myself and my own family and da D they think you know if I do this I'm protecting my family I'm helping my country we will live in peace

it should provide one task only and do it well

Well-thought-out, idiomatic APIs

When building the Droplet Console, we had a few options to support SSH keys-based authentication. The most straightforward way would be to directly allow the customer to specify a private key that is already set up for accessing the Droplet. However, there are some problems with this solution:

UNIX philosophy: Do one thing and do it well!

vaguely worded constitutional provision like the Second Amendment

As a political gesture to the Anti-Federalists—a gesture highlighted by the Second Amendment’s prefatory reference to the value of a well-regulated militia—express recognition of the people’s right to arms was something of a sop.

Auto-update aside, you might also have found it hard to find a Chrome binary with a specific version. Google intentionally doesn’t make versioned Chrome downloads available, since users shouldn’t have to care about version numbers—they should always get updated to the latest version as soon as possible. This is great for users, but painful for developers needing to reproduce a bug report in an older Chrome version.

What I have seen is situations where things were made horribly complicated to get around protections for which there was no need, and to try to guard the consistency of data structures that were horribly over-complicated and un-normalized.

Have you ever: Been disappointed, surprised or hurt by a library etc. that had a bug that could have been fixed with inheritance and few lines of code, but due to private / final methods and classes were forced to wait for an official patch that might never come? I have. Wanted to use a library for a slightly different use case than was imagined by the authors but were unable to do so because of private / final methods and classes? I have.

In recent git versions, git restore is supposed to be a "better" way to revert undesired local changes than the overloaded checkout. Great, that sounds reasonable - a nice simple purpose-built tool for a common operation.

For most Americans, poverty is seen as an individualized conditionthat exclusively affects those individuals, their families, and perhaps theirneighborhoods. Rarely do we conceptualize a stranger’s poverty as having adirect or indirect effect on our own well-being.

In v3, svelte-preprocess was able to type-check Svelte components. However, giving the specifics of the structure of a Svelte component and how the script and markup contents are related, type-checking was sub-optimal. In v4, your TypeScript code will only be transpiled into JavaScript, with no type-checking whatsoever. We're moving the responsibility of type-checking to tools better fit to handle it, such as svelte-check, for CLI and CI usage, and the VS Code extension, for type-checking while developing.

Computers can only deal with well-structured problems

Viral FeedbackProviding scientific perspectives on public information regarding COVID-19

highly recommended that the resulting image be just one concern per container; predominantly this means just one process per container, so there is no need for a full init system

Doing everything PID 1 needs to do and nothing else. Things like reading environment files, changing users, process supervision are out of scope for Tini (there are other, better tools for those)

Glyph 0 must be assigned to a .notdef glyph. The .notdef glyph is very important for providing the user feedback that a glyph is not found in the font. This glyph should not be left without an outline as the user will only see what looks like a space if a glyph is missing and not be aware of the active font’s limitation.

Indicative of howclose many Americans are to poverty, a recent study by the Federal ReserveBank found that 37 percent of Americans do not have enough savings put asideto protect them from a $400 emergency.20

What have been the decisive positive and negative changes andchallenges in the teachers

Finally, teachers’, principals’ andstudents’ engagement and well-being during the pandemic

Calling a software convention "pretty 90s" somewhat undermines your position. Quite a lot of well-designed software components are older than that. If something is problematic, it would be more useful to argue its faults. When someone cites age to justify change, I usually find that they're inexperienced and don't fully understand the issues or how their proposed change would impact other people.

Time Well Spent

I have never seen the @Stale bot or any directly equivalent to it achieve a net positive outcome. Never. It results in disgruntled people, extra expenditure of effort (for reporters and maintainers), real stuff getting lost when people get fed up with poking the bot (I have no intention of poking it further), and more extensive filing of duplicates. You say a simple comment dismisses it, but it doesn’t—it only does this time. Next time, it continues to annoy. This is an issue tracker. Use labels, projects, milestones and the likes for prioritising stuff. Not sweeping stuff under the carpet.

Closing issues doesn’t solve anything. Closing issues in GitHub just sweeps them under the carpet and helps everyone to forget about them, which is just not what you want—the fact that GitHub search excludes closed items by default is a large part of the problem with it. As applied to software projects with general-purpose issue trackers, the @Stale bot is fundamentally phenomenally bad idea, a road paved with good intentions. I presented an actionable alternative: labels. Possibly automatically applied, but it’s certainly better to spend a little bit of time on manual triage. It honestly doesn’t take long to skim through a few hundred issues and bin them into labels. 609 open issues? That’s honestly not a problem. Not at all. There’s nothing wrong with having a large number of issues open, if they do correspond to real things—even things that you may not expect to get to for years, if ever, because that might change or someone might decide they want to deal with one. Closing issues that aren’t dealt with is bad. Please don’t do it.

If you dig into the details, you will see that the TypeScript team take breaking changes very seriously and with consideration.

which seems to resolve the issue for me and makes no casts, ensuring that Typescript can keep doing its good job of widening as much as necessary and narrowing as much as possible without me having to claim I know better than the compiler. I'm posting it here since it doesn't seem to have been mentioned anywhere.

Pipe assessment is never an elective activity. It's usually forced upon you when the toilets refuse to flush and wastewater comes up instead of going down.

# This is a configuration file for direnv (https://direnv.net/), a tool that # allows you to automatically set up environment variables based on the current # directory. If you install and enable direnv, then this file will ensure that # `nvm` is installed in your home directory and that the version of Node in # .nvmrc is selected.

The WebSocket Protocol is designed on the principle that there should be minimal framing (the only framing that exists is to make the protocol frame-based instead of stream-based and to support a distinction between Unicode text and binary frames). It is expected that metadata would be layered on top of WebSocket by the application Fette & Melnikov Standards Track [Page 9] RFC 6455 The WebSocket Protocol December 2011 layer, in the same way that metadata is layered on top of TCP by the application layer (e.g., HTTP). Conceptually, WebSocket is really just a layer on top of TCP that does the following: o adds a web origin-based security model for browsers o adds an addressing and protocol naming mechanism to support multiple services on one port and multiple host names on one IP address o layers a framing mechanism on top of TCP to get back to the IP packet mechanism that TCP is built on, but without length limits o includes an additional closing handshake in-band that is designed to work in the presence of proxies and other intermediaries Other than that, WebSocket adds nothing. Basically it is intended to be as close to just exposing raw TCP to script as possible given the constraints of the Web. It's also designed in such a way that its servers can share a port with HTTP servers, by having its handshake be a valid HTTP Upgrade request. One could conceptually use other protocols to establish client-server messaging, but the intent of WebSockets is to provide a relatively simple protocol that can coexist with HTTP and deployed HTTP infrastructure (such as proxies) and that is as close to TCP as is safe for use with such infrastructure given security considerations, with targeted additions to simplify usage and keep simple things simple (such as the addition of message semantics).

This is one of the more-satisfying ruby expressions I've seen in a long time. I can't say that it also has prosaic transparency, but I think seeing it teaches important things.

Induction does not pander, but gives you the satisfaction of mastering an imaginary yet honest set of physical laws.

It’s fun but when would we ever use things like this in actual code?When it’s well tested, commented, documented, and becomes an understood idiom of your code base.We focus so much on black magic and avoiding it that we rarely have a chance to enjoy any of the benefits. When used responsibly and when necessary, it gives a lot of power and expressiveness.

The number of lives lost around the world over the past year and a half is about equal to the population of Los Angeles or the nation of Georgia. It is three times the number of victims killed in traffic accidents around the globe per year.

There are many projects that does not use the master branch as default. For example, Next.js uses the canary branch, the npm CLI and many more other projects uses stuff like prod, production, dev, develop, release, beta, head.

“The data does not exist independently in the world, nor is it generated spontaneously. Data is constructed by people, from people,” (source 1).

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.

I've been thinking more about how to best do this. The preferred way might be to use the same domain and have an application load balancer like nginx split traffic on the URL path (e.g. /api). This is for two reasons. Firstly, you might not necessarily want to cookie the primary/apex domain and have the cookie shared across all subdomains. You also might not want to do CORS because preflight requests add latency and CORS adds complication.

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.

Also cross-compatibility with mail clients can be hairy, so you should see what the industry experts are doing.

“Who cares? Let’s just go with the style-guide” — to which my response is that caring about the details is in the heart of much of our doings. Yes, this is not a major issue; def self.method is not even a code smell. Actually, that whole debate is on the verge of being incidental. Yet the learning process and the gained knowledge involved in understanding each choice is alone worth the discussion. Furthermore, I believe that the class << self notation echoes a better, more stable understanding of Ruby and Object Orientation in Ruby. Lastly, remember that style-guides may change or be altered (carefully, though!).

You can't avoid the comparisons to Carcassonne even though the scoring mechanic is very different. It just looks the same, and the tile placement phase feels close enough to be familiar. However, this familiarity starts to nag at you, only adding to the frustration when tile placement is clumsy and luck-driven unlike Carcassonne. The comparison is not favourable for Fjords.

It's a matter of readability I guess.

On the other hand, you state that a certain thing behaves_like a shared example group.

A Game-design MasterpieceTake one simple game mechanic, and make the absolute most of it – that's exactly what the developers of Jim is Moving Out did, and it worked really well! The core of this game is stunningly simple: a few little boxes (furniture) inside a big box (Jim's house), one or two flying fellas (the players) and a physics engine. Think about the most creative ways you could make this into a game. Anything you think about, this game did it. What if you had to squeeze through narrow holes without breaking too much furniture? It's in the game. What if the room had wheels? Yep, it's there too. What if one of the walls was missing and you had to avoid losing the furniture? The whole co-op is about this. Zero gravity? Yes, even that is in the game.

With all this “monetization” happening around Trailblazer, we will also make sure that all free and paid parts of the project grow adult and maintan an LTS - or long-term support - status. Those are good news to all you users out there having been scared to use gems of this project, not knowing whether or not they’re being maintained, breaking code in the future or making your developers addicted to and then cutting off the supply chain. Trailblazer 2.1 onwards is LTS, and the last 1 ½ years of collaboration have proven that.

This issue hasn’t been deemed a high enough priority to be fixed yet. It will be addressed one day, I’m sure. There are many issues in GLib which many people on the internet think are important.

Write modules that do one thing well. Write a new module rather than complicate an old one.

In the real world, we are faced with the completely unfair constraint of being human while writing programs and while debugging them, and none of these costs can ever be reduced to zero.

Focus is better than features.

It is about balancing the twin needs of writing good software, and writing any software at all.

Webshim is also more than a polyfill, it has become a UI component and widget library. Webshim enables a developer to also enhance HTML5 capable browsers with more highly customizable, extensible and flexible UI components and widgets.

So, where did J.C. Penney go wrong? Well, while we admire their attempt to change, they attempted to destroy over a century’s worth of price conditioning consumers have been through with department stores and pricing in general. They weren’t completely off base, as consumers with more and more access to information (comparison shopping engines, consumer reports, etc.), are beginning to realize that the value of products is determined much differently than a sticker would suggest. Yet, assuming that most soccer moms (and dads) wouldn’t fall prey to the colorful print ads tucked within the comics section in the Sunday paper, overlooks how much the majority of consumers value “winning” the retail game. Simply, deflating the perceived value causes customers to value the actual product less.

But so far everything brought up has just been about the relative advantages of checked exceptions, and that issue is closed. We won't do it.

provide interfaces so you don’t have to think about them

note that TRB source code modifications are not proprietary

The new 2.1 version comes with a few necessary but reasonable changes in method signatures. As painful as that might sound to your Rails-spoiled ears, we preferred to fix design mistakes now before dragging them on forever.

The assert method is used by all the other assertions. It pushes the second parameter to the list of errors if the first parameter evaluates to false or nil.

In object-oriented programming, information hiding (by way of nesting of types) reduces software development risk by shifting the code's dependency on an uncertain implementation (design decision) onto a well-defined interface. Clients of the interface perform operations purely through it so if the implementation changes, the clients do not have to change.

Consequently, you act irresponsibly when you adopt any programming practice simply because "that's the way you're supposed to do things."

My point is that you should not program blindly. You must understand the havoc a feature or idiom can wreak. In doing so, you're in a much better position to decide whether you should use that feature or idiom. Your choices should be both informed and pragmatic.

It makes me happy to see people actually think about things and not just accept a shitty API.

Trust me, I thought a lot about #validate and its semantics, and I am gonna make it even more "SRP" by making Form#errors and #valid? semi-public. All that happens via #validate reducing the possible wrong usage for users.

Unlike naming children, coding involves naming things on a daily basis. When you write code, naming things isn’t just hard, it’s a relentless demand for creativity. Fortunately, programmers are creative people.

First of all, we want names to exhibit truth and beauty: to be the right names, and to make our code clean and beautiful. At least, this is what we want to think about our code, but naming’s importance is far more practical.