It’s easy to think of 1fr as being “one part of the space in the grid container” when it is really one part of the space left over.

Why is CORS important? Currently, client-side scripts (e.g., JavaScript) are prevented from accessing much of the Web of Linked Data due to "same origin" restrictions implemented in all major Web browsers. While enabling such access is important for all data, it is especially important for Linked Open Data and related services; without this, our data simply is not open to all clients. If you have public data which doesn't use require cookie or session based authentication to see, then please consider opening it up for universal JavaScript/browser access. For CORS access to anything other than simple, non auth protected resources

A common and simplistic type of statistical testing is a z-test, which tests the statistical significance of a sample mean to the hypothesized population mean but requires that the standard deviation of the population be known, which is often not possible. The t-test is a more realistic type of test in that it requires only the standard deviation of the sample as opposed to the population's standard deviation.

if the P-test fails to reject the null hypothesis then the test is deemed to be inconclusive and is in no way meant to be an affirmation of the null hypothesis.

You must use a laptop or desktop computer You must use Chrome as your browser (we recommend using the most current version) You must allow third-party cookies (a setting in Chrome)

This explains how much X varies from its mean when Y varies from its own mean.

People really don't stress enough the importance of enjoying what you're programming. It aids creativity, makes you a better teammate, and makes it significantly easier to enter a state of flow. It should be considered an important factor in choosing a web development framework (or lack thereof). Kudos!

These are sequential because build:ssr imports the public/index.html that build:dom produces.

delete will only work on properties whose descriptor marks them as configurable.

The delete operator does not directly free memory, and it differs from simply assigning the value of null or undefined to a property, in that the property itself is removed from the object.

It is very important that "production ready" UI libraries are available because otherwise the use of Svelte cannot be argued. A key point would be to make it easy possible that people can contribute

After i've stabilized the library i can start to discuss about adding new components and features!

I agree, it would be great to join forces and speed up development... Svelte really needs one safe material library option.

this in particular comes from the addressee

To bundle this in your own code, use a Sass processor (not a Sass Svelte preprocessor, but a Sass processor)

Overshoot is used on important dialogs to convey a sense of urgency.

This module should not be used in other npm modules since it modifies the default require behavior! It is designed to be used for development of final projects i.e. web-sites, applications etc.

The resolving process is basically simple and distinguishes between three variants: absolute path: require("/home/me/file") relative path: require("../src/file") or require("./file") module path: require("module/lib/file")

The meaning of the word "modularity" can vary somewhat based on context. The following are contextual examples of modularity across several fields of science, technology, industry, and culture:

We expect a certain pattern when validate devtool name, pay attention and dont mix up the sequence of devtool string. The pattern is: [inline-|hidden-|eval-][nosources-][cheap-[module-]]source-map.

Using as * adds a module to the root namespace, so no prefix is required, but those members are still locally scoped to the current document.

This is linux. Ouput first, formatting second. systemctl --no-pager -l should be the default.

You may want to execute validations in a given specific order (this can be tricky especially when you have got asynchronous validations).

This is a philosophical issue, I think. People (and presumably form libraries) have different definitions of what "dirty" means. Yours: "The field has ever been edited" Mine: "The value of the field is different from the initial value"

For performance reasons, $: reactive blocks are batched up and run in the next microtask. This is the expected behavior. This is one of the things that we should talk about when we figure out how and where we want to have a section in the docs that goes into more details about reactivity. If you want something that updates synchronously and depends on another value, you can use a derived store:

In so doing, we argue that learning analytics needs to build on and better connect with the existing body of research knowledge about learning and teaching.

First of all, we solved our problem! As demonstrated here our app is happily running again.

Yeah I see what you're saying. In my case, I had a group of classes that relied on each other but they were all part of one conceptual "module" so I made a new file that imports and exposes all of them. In that new file I put the imports in the right order and made sure no code accesses the classes except through the new interface.

Doing so also means adding empty import statements to guarantee correct order of evaluation of modules (in ES modules, evaluation order is determined statically by the order of import declarations, whereas in CommonJS – and environments that simulate CommonJS by shipping a module loader, i.e. Browserify and Webpack – evaluation order is determined at runtime by the order in which require statements are encountered).

Specifically, since Root, Rule and AtRule all extend Container, it's essential that Container is evaluated (and therefore, in the context of a Rollup bundle, included) first. In order to do this, input.js (which is the 'gateway' to all the PostCSS stuff) must import root.js, root.js must import rule.js before it imports container.js, and rule.js must import at-rule.js before it imports container.js. Having those imports ensures that container.js doesn't then try to place Root, Rule or AtRule ahead of itself in the bundle.

Replaced nested `require` statements with `import` declarations for the sake of a leaner bundle. This entails adding empty imports to three files to guarantee correct ordering – see https://github.com/styled-components/styled-components/pull/100

Modules from the following layer can require anything from all the previous layers, but not vice versa.

Omitted details change everything here. There won't be circular dependency because unused import is skipped. Consider providing stackoverflow.com/help/mcve .

Note that the <WarningEngine/> component must be at the bottom of the form to guarantee that all the fields have registered.

Our long-term vision is computational intelligence based on collective intelligence.

Encoding is dependent on the type of output - which means that for example a string, which will be used in a JavaScript variable, should be treated (encoded) differently than a string which will be used in plain HTML.

Balanced named tags is a critical syntactic feature of the XML-style notation.

A style guide is about consistency. Consistency with this style guide is important. Consistency within a project is more important. Consistency within one module or function is the most important.

The clean-up function runs before the component is removed from the UI to prevent memory leaks. Additionally, if a component renders multiple times (as they typically do), the previous effect is cleaned up before executing the next effect. In our example, this means a new subscription is created on every update.

The contrast between these two responses reveals a shift from projection onto an object to engagement with a subject

human habit of making assump-tions based on perceptions of behavior

people did not care if their life narratives were really understood. The act of telling them created enough meaning on its own

trust in Eliza did not speak to what they thought Eliza would understand but to their lack of trust in the people who would understand.

human purposes of believable digital companions that are evocative but not authentic.

The feelings they elicit will reflect human vulnerabilities more than ma-chine capabilities

by the time we face the reality of computational devices that are indistinguishable from people, and thus able to pass our own Turing test, we will no longer care about the test.

“When I wake up in the morning and see her face [the robot’s] over there, it makes me feel so nice, like somebody is watching over me.”

l’intérieur des locaux scolaires

There's one downside to Reacts reactivity model - the hooks (useState and useEffect) have to always be called in the same order and you can't put them inside an if block.

createState and createSignal are improvements over React's useState as it doesn't depend on the order of calls.

The readable store takes a function as a second argument which has its own internal set method, allowing us to wrap any api, like Xstate or Redux that has its own built in sub­scrip­tion model but with a slightly different api.

“every courageous and incisive measure to solve internal problems of our own society, to improve self-confidence, discipline, morale and community spirit of our own people, is a diplomatic victory over Moscow worth a thousand diplomatic notes and joint communiqués. If we cannot abandon fatalism and indifference in the face of deficiencies of our own society, Moscow will profit.”

exclusivement, sous peine de nullité

Those banners should really be reserved for the important stuff. Because they're not, I've developed a reflex to immediately close those banners without paying attention. It's almost the same as blocking it with an ad-blocker; which defies the (original) purpose of banners.

Your problem is that you were returning the rejected loginDaoCall, not the promise where the error was already handled. loginApi.login(user, password) did indeed return a rejected promise, and even while that was handled in another branch, the promise returned by the further .then() does also get rejected and was not handled.

Auto-subscription only works with store variables that are declared (or imported) at the top-level scope of a component.

let:hovering={active}

let:active={hovering}

User experience above all

balancing developer and user experience

Rollup will only resolve relative module IDs by default.

But library users are more numerous, and so their needs are more important.

If calling query() results in calls to Svelte's context API, then it needs to be called synchronously during component initialization.

feel like there needs to be an easy way to style sub-components without their cooperation

The problem with working around the current limitations of Svelte style (:global, svelte:head, external styles or various wild card selectors) is that the API is uglier, bigger, harder to explain AND it loses one of the best features of Svelte IMO - contextual style encapsulation. I can understand that CSS classes are a bit uncontrollable, but this type of blocking will just push developers to work around it and create worse solutions.

This has the merit of simplicity and obviousness, but it's not particularly ergonomic: it signals that we don't consider component themeability to be a problem worth solving properly.

Notice that all tags start with a lower case letter. This is different to other NativeScript implementations. The lower case letter lets the Svelte compiler know that these are NativeScript views and not Svelte components. Think of <page> and <actionBar> as just another set of application building blocks like <ul> and <div>.

In fact, you might use the two together. Since context is not reactive, values that change over time should be represented as stores:

In graph theory, a tree is a connected acyclic graph; unless stated otherwise, in graph theory trees and graphs are assumed undirected. There is no one-to-one correspondence between such trees and trees as data structure.

Free software thus differs from: proprietary software, such as Microsoft Office, Google Docs, Sheets, and Slides or iWork from Apple. Users cannot study, change, and share their source code. freeware, which is a category of proprietary software that does not require payment for basic use.

Co-hyponyms are labelled as such when separate hyponyms share the same hypernym but are not hyponyms of one another, unless they happen to be synonymous

Note that the double quotes around "${arr[@]}" are really important. Without them, the for loop will break up the array by substrings separated by any spaces within the strings instead of by whole string elements within the array. ie: if you had declare -a arr=("element 1" "element 2" "element 3"), then for i in ${arr[@]} would mistakenly iterate 6 times since each string becomes 2 substrings separated by the space in the string, whereas for i in "${arr[@]}" would iterate 3 times, correctly, as desired, maintaining each string as a single unit despite having a space in it.

If all your styles are !important, then none of your styles are important.

Using !important in your CSS usually means you’re narcissistic & selfish or lazy. Respect the devs to come…

The meta charset information must also be the first child of the <head> tag. The reason this tag must be first is to avoid re-interpreting content that was added before the meta charset tag.

During the fragment hit-to-lead process, we typically synthesize 50–100 compounds to increase the binding affinity from millimolar to nanomolar, and we routinely generate multiple lead series for each target

the most potent fragment is often not the best starting point for hit-to-lead chemistry.

Although better cross-validation would provide increased confidence in fragment hits, there is a danger that this may also result in the systematic selection of more potent hits,

great importance should be placed on accurately characterizing the solubility of a fragment library

observe a correlation of 30–40% using these two techniques.

Another area of active debate centres on the lack of correlation of fragment hits obtained using different detection techniques

Computer architecture advancements has led to the rise of multi-core, in-memory DBMSs that employ efficient transaction man-agement mechanisms to maximize parallelism without sacrificingserializability.

Les droits définis par le décret s’appliquent aux associations de parents représentées au conseil d’école ou au conseil d’administration ainsi qu’à celles représentées au Conseil supérieur de l’éducation, au conseil académique ou au conseil départemental de l’éducation nationale même si elles n’ont pas d’élus dans les instances de l’école ou de l’établissement.

when: never would be redundant here, this is implied any time rules are listed.

In a basic configuration, GitLab runs a pipeline each time changes are pushed to a branch. If you want the pipeline to run jobs only when merge requests are created or updated, you can use pipelines for merge requests.

doing the wrong thing quickly is a good way to bankrupt us and our customers

The order is important.

It’s important to note that where the GDPR applies, intended use factors into whether or not consent is required as even statistical data can fall under “profiling” or “monitoring” depending on how the data is being used.

The Microsoft Calculator program uses the former in its standard view and the latter in its scientific and programmer views.

In the context of first-order logic, a distinction is maintained between logical validities, sentences that are true in every model, and tautologies, which are a proper subset of the first-order logical validities. In the context of propositional logic, these two terms coincide.

It may be the case that several sufficient conditions, when taken together, constitute a single necessary condition (i.e., individually sufficient and jointly necessary)

The qualifier of ‘certain circumstances’ is important to highlight here, because it’s often the context in which information exists that determines whether it can identify someone.

However, please note the following: it will depend on how those subdomains are defined. Are they just subsections of a project that belongs together like help.example.com or blog.example.com (and many other possible arrangements that are part of one and the same setup)? In such a case, using the same policy is appropriate. Problems arise when completely different projects which have little to do with one another and whose data collection practices also differ so significantly that they require different privacy policies.

Now, do I care which one you use? No. As long as you test your code, I am happy. A professional developer should be able to work in either one of these because they essentially do the same thing: test your code.

A single consent form is useful when consent is requested for a single purpose. Here: analytics

However, translating/interpreting is not the only job a polyglot can have. If we speak about a world-language bearer (English, Spanish, Chinese, etc.), the range of possibilities broadens. My uncle has once told me: "You have English, now you can learn anything." The point is, language is a crucial aspect of development both in terms of career and social life. Language(s) is(are) the basis. You move further on learning new knowledge and acquiring new skills with time. Though, they are not limited to the language you know.If you are talented at languages, you can decide which one you are interested in and study it. Once you have decided, you then choose the particular subject field you want to work in. If you are talented "only" at languages, other ways are open to you. You can be a teacher, tutor, again translator/interpreter, etc.All I want to say is language is power. Where I come from, it is a treasure. I do not know what is it like to be a citisen of a large, highly-developed, economically stable, and successful country. Though, I know for sure, if you know and love languages, you will find your place anywhere.

If something is important but not urgent - like complimenting or encouraging the entire team - use email or post in the channel without @-mentioning the team.

We commit to build the load testing tool with the best developer experience, k6, and developing it in the open with the community, read our document on stewardship of the OSS k6 project. We believe this is key and the necessary foundation to build great developer tooling.

we believe that developer tools should be open source to allow for a community to form and drive the project forward through discussions and contributions. Hence why we built k6, the load testing tool we’ve always wanted ourselves!

We check in our code at the entry point of a pipeline, version control (Git and Github in our case), and then it’s taken through a series of steps aimed at assuring quality and lowering risk of releases. Automation helps us keep these steps out of our way while maintaining control through fast feedback loops (context-switching is our enemy). If any step of the pipeline breaks (or fails) we want to be alerted in our communication channel of choice (in our case Slack), and it needs to happen as quickly as possible while we’re in the right context.

With k6, our goal has always been to create the best load testing tool for the modern working developer and that we do this in collaboration with the k6 community. Our revenue will not come from k6 directly, but from premium value creating offers based on k6. These offers will be made available at https://loadimpact.com. Load Impact premium offers will have focus on providing further simplicity, productivity and ease to use functionality.

We believe the key to Load Impact’s long-term success as a Company is to foster an active community of users around k6 as an open source project. To achieve this long-term goal, it is vital that we do not withhold new features from k6 based on whether or not they compete with our SaaS offering.

People hate asking sensitive questions. However, it turns out that people don’t hate being asked sensitive questions. So talking around difficult questions in research interviews is a waste of time and money

Aside from testing, we place high value in documenting code. It's our legacy for anyone who will be working with our codebase in the future. Fortunately, having a component library like Storybook allows us to document components visually and declaratively. Storybook provides a developer with all the information needed to understand the structure and state of a component.

Method

They have made the mistake of believing that you can optimize life. That if they follow the instructions of some study they will find pure bliss. They will finally escape being human.

You overlook the fact you are capable of figuring things out on your own

Mitosis is a method of cell division in which a cell divides and produces identical copies of itself.

systematic domination of women by men

f(x)=x2

Pair-share: What’s the next counting-by-10 number on the line after 26? Record several student responses on the board.

Simply put, your frog is the most important task. It is the thing that moves the needle the most towards your ideal future. It is probably very important, but not very urgent. So our advice (and Brian Tracy’s as well) is to make sure you tackle this MIT at the beginning of your day when you have the most energy and willpower available. Tackling your MIT first thing is extremely important!

If I were to summarize the book in a single statement, it would be that you should do your most important task (MIT) first thing in the morning.

Compatibility with any process.

Continuous Improvement (Kaizen)It occurred to me rather late that continuous improvement is a risk management strategy.

people don’t make any difference between planning, estimating and scheduling.

If someone claims that they can effectively schedule the work of a team of knowledge workers more than one week in the future (even this is questionable), slap them in the face and don’t talk to them ever again.

Scheduling work means that we fix the start and end date of each individual task. Scheduling in knowledge work is a waste. Period.

o leaving a a longer a trade history on there would be useful is what attracts.

awesome. Maybe like 100 trades back or something because I've run into that same issue on some of the other sites. Even the exchanges themselves, despite being bittrex being such a shitty place to trade, they actually do a good job of leaving, you know, 10 pages of 10 trades each or something on there for you to look. Which is nice because I do find a lot of people or an algorithm will place a really big sell order and an immediate buy right after, at the previous limit. Um, say a sell order for 100 coins and then a one person, one percent of one coin. Or point 01 at the buy order back. So it gets hidden and the candles may show up green. But if you're not looking at the order book, you're going to miss that.

Um, the one thing I did want to see some more of is like under your portfolio, uh, when you're going through the, you know, the rebalancing, the correlation and the optimization, um, would just be some more information about, okay, here's how we did, um, are efficient frontier. Like here's the calculation we used. I know it's one basic calculation, but there are different parameters that people can use in them based on the risk above. So just having more general research on there, just saying, or maybe a link to another page that explains like, here's the calculations that we're using. Here's the portfolio theory, with the correlation index, you know, so setting that up, just showing people some math behind it.

but the order book and the trade history are really important to me.

e benefit. Like I don't have any benefit in blocfolio, like sharing my position size and i know what my position size is, i look at it 10 times a day. I don't see any need for me to put it into blocfolio. I'm mostly concerned with just price data.

virtually every single DevOps success story is based on a multi-year kaizen-based continuous improvement strategy