many people are complex systems thinkers even though they don't know it

well I'll start with two extremely optimistic points

in many parts of the world you see a kind of conservative suicide that conservatives are abandoning their kind of traditional role to slow down and conserve 00:26:09 institutions and traditions and so forth and they still call themselves conservatives but they become this kind of new radical party which is more about ignoring traditions and destroying 00:26:23 institutions and then it becomes the job of liberals to be the audience of the institutions

excessive expectations and reliance on CCUS

In API design, exceptional use cases may justify exceptional support. You design for the common case, and let the edge case be edge. In this case, I believe lib deserves ad-hoc API that allows users to do exactly that in one shot:

I think we are a victim of behavioural norms and so many of the apps that I use have this pattern. That's not to say it's the right behaviour, but it may be hard to break the pattern for users.

Comments may be turned off across YouTube

Comments are turned off.

Recent work has revealed several new and significant aspects of the dynamics of theory change. First, statistical information, information about the probabilistic contingencies between events, plays a particularly important role in theory-formation both in science and in childhood. In the last fifteen years we’ve discovered the power of early statistical learning.

Speed is great but if it doesn't conform to the specification, that's not a great case for using it for future development

If we hand most, if not all responsibility for that exploration to the relatively small number of people who talk at conferences, or have popular blogs, or who tweet a lot, or who maintain these very popular projects and frameworks, then that’s only a very limited perspective compared to the enormous size of the Ruby community.

Please can we (a) retain case information from the email address the student uses to set up their account (in case their mailbox is case sensitive), and use that when sending password reset emails, etc., but also (b) when checking credentials for login or setting up an account, treat the email address as non-case-sensitive. The upshot would be if someone registered with Student@City.ac.uk, all emails would go to Student@City.ac.uk, but the student would be able to log in with student@city.ac.uk, and if someone later tried to set up an account with student@city.ac.uk they'd be told that the user already exists.

Although there's an argument for keeping case sensitivity for the local mailbox (as they can be case sensitive, depending on how they're set up, though I haven't come across case sensitivity in university emails), the domain part of the email address is not case sensitive and should not be treated as such. Please can we (a) retain case information from the email address the student uses to set up their account (in case their mailbox is case sensitive), and use that when sending password reset emails, etc., but also (b) when checking credentials for login or setting up an account, treat the email address as non-case-sensitive. The upshot would be if someone registered with Student@City.ac.uk, all emails would go to Student@City.ac.uk, but the student would be able to log in with student@city.ac.uk, and if someone later tried to set up an account with student@city.ac.uk they'd be told that the user already exists.

If you are storing email addresses then you probably should store them in their original case (the recipient at least) to be safe. However, always compare them case-insensitively in order to avoid duplicates.

However, it's difficult to rely on a case-sensitive email address in the real world because many systems (typically ones that have to handle data merging) don't preserve case. Notably systems that use email addresses for user IDs, or any system that has to collate data from multiple sources (CRMs, email broadcast systems, etc) will either normalise case or treat them case-insensitively.

However, for all practical purposes in the modern age, I believe you can consider email addresses to be case insensitive.

a SHOULD is always trumped in RFCs by a MUST. The fact that hosts SHOULD do something means that they might not and I just wanted reassurance that, in reality, the SHOULD is a bit more widely adopted than its definition implies.

While email addresses are only partially case-sensitive, it is generally safe to think of them as case insensitive. All major providers, such as Gmail, Yahoo Mail, Hotmail, and others, treat the local parts of email addresses as case insensitive.

According to RFC 5321, the local part of the email address is case sensitive. This means that, in theory, SoMething@something.com is not the same as something@something.com. However, email providers have the liberty to treat the local parts as both case sensitive and case insensitive.

Are Email Addresses Case Sensitive? Technically, the answer is yes. However, email addresses are typically not case sensitive; if you type your email address into a form and accidentally capitalize one or two letters, it probably won’t prevent the sender from emailing you.

The local part does, in fact, take the case into account, as per RFC 5321. However, Email Service Providers (ESPs) are aware of the potential confusion that could result from allowing upper-case letters.

In short, while it’s technically possible to make the part before @ case sensitive, most popular email servers do not allow that. 

Most big email providers like Gmail, Outlook and even company email address hosted on Google Suite are not case sensitive. Just to avoid any unnecessary confusion. However, in extreme cases, some large companies, implement case sensitivity on their server as some people can often have the same first and last name. But in general, this creates more confusion, than the usability, which is why most standard email providers avoid case sensitivity. 

Either way, at some point almost everyone started treating addresses as case-insensitive.

Despite it being commonplace to “fix up” email addresses by lowercasing them — or, in financial/government contexts, uppercasing them — email addresses are clearly defined as case-sensitive in the only standard that matters.

Since using case insensitivity is so widespread, take their sign up email address and make it lower case. Whenever they try to log in, convert that to lowercase as well, for comparison purposes, when you go to see if the user exists. As far as sign up and sign in go, do a case insensitive comparison. If the person signs up as Steve@example.com, you'll still want to allow them to sign in later with steve@example.com or sTeVE@example.com.

But you should also keep track of the email address that they signed up with in a case sensitive fashion. Any time you send an email to them, be sure to send it with that original casing. This allows the email server to handle it however it feels like it needs to. So even though the person may always be signing in to your site with steve@example.com, if they signed up as Steve@example.com, you'll always send email to Steve@example.com, just to be safe.

The de facto standard is to treat local mailboxes as case insensitive, but the official standard says case matters (though even the official standard mentions the de facto standard).

So yes, the part before the "@" could be case-sensitive, since it is entirely under the control of the host system. In practice though, no widely used mail systems distinguish different addresses based on case.

In short, you are safe to treat email addresses as case-insensitive.

Since the case sensitivity of email addresses can create confusion and delivery problems, most email providers and clients either fix the case if the email address is entered in the wrong case, or they ignore upper-case entries. Not many email services or ISPs enforce case-sensitive email addresses.

Stop to think about "normal app" as like desktop app. Android isn't a desktop platform, there is no such this. A "normal" mobile app let the system control the lifecycle, not the dev. The system expect that, the users expect that. All you need to do is change your mindset and learn how to build on it. Don't try to clone a desktop app on mobile. Everything is completely different including UI/UX.

gaga's third question where are we going is what i want to address in these talks 00:05:26 it may seem unanswerable who can foretell the human course through time but i think we can answer it in broad strokes by answering the other two questions first 00:05:40 if we see clearly what we are and what we've done we can recognize human behaviors that persist through many times and cultures and knowing these can tell us what we 00:05:52 are likely to do and where we are likely to go from here

the artist managed to harness his grief to produce a vast painting more a mural in conception than a canvas in which like the victorian age itself he demanded 00:04:31 new answers to the riddle of existence he wrote the title boldly on the image three childlike questions simple yet profound where do we come from 00:04:46 what are we where are we going the work is a sprawling panorama of enigmatic figures amid scenery

When you call 'foo' in Ruby, what you're actually doing is sending a message to its owner: "please call your method 'foo'". You just can't get a direct hold on functions in Ruby in the way you can in Python; they're slippery and elusive. You can only see them as though shadows on a cave wall; you can only reference them through strings/symbols that happen to be their name. Try and think of every method call 'object.foo(args)' you do in Ruby as the equivalent of this in Python: 'object.getattribute('foo')(args)'.

Note though, that this only works when you're already using git for your dependency

People know it’s bad but not how bad. This gap in understanding remains wide enough for denialists and minimisers to legitimise inadequate action under the camouflage of empty eco-jargon and false optimism. This gap allows nations, corporations and individuals to remain distracted by short-term crises, which, however serious, pale into insignificance compared with the unprecedented threat of climate change.

个人学习可能取决于他人行为的主张突出了将学习环境视为一个涉及多个互动参与者的系统的重要性

ned the art of notetaking for themselves that this pamphletis prepared. It does not seem wise to attempt to lay down any verystringent rules on the subject. We can only suggest the more generalmethods from which every man can work out his own particular system.

Primary keys and foreign keys are the fundamental building blocks of the relational database because these are the components that make the relationships work while allowing tables to be accessed independently. One-to-many relationships between primary keys and foreign keys are thus defined as referential constraints in the physical database

this has a few sections we're going to first talk about snakes and 00:12:58 elephants then about this idea of the atman it's the sanskrit name for itself the self that's the english word and the soul or suitcase we might say in christian theology then i will introduce 00:13:10 you to my favorite illusion because it's fun and it will help us to get a fix on what we're doing and then i will argue that in fact you do really think that you have a self so there is a point to all of this there 00:13:21 would be no point if we didn't think we had self there would be no point in refuting them and then we'll fight try to ask why you think you have a self so that's what we're going to do in the first part of tonight's talk

This was originally disallowed because #5907 was opened asking for different behavior in this situation that we didn't want to allow, and so we decided to make it a compiler error rather than have confusing behavior in that situation.

The console needs to be readable in development and to provide the best DX I have to design my libraries in ways that prevent these warnings. This results in design decisions that are detrimental to functionality and/or code readability/simplicity.

I just spent a day dismantling a model, trying to find the cause of the silent rollback - taking out every association, every validation, every callback, whittling down all the code in the transaction, only to finally discover that it was return true that was the cause of it all. Or yes, an exception!

Instead of imposing a ‘rational’ order on the fragments,Barthes used the ‘stupid’, arbitrary, obvious order of the alphabet(which he also most often followed when he was classifying his indexcards): this was how he proceeded in ‘Variations on Writing’ and inRoland Barthes par Roland Barthes. This was how he achieved anindividual identity, surrendering to his tastes and to concrete littleidiosyncrasies.

Deutsch’s index, then, did not constitute the systematic and overarching view ofJewish history and contemporaneous Jewish issues that Deutsch had initially hoped tocreate. Instead, it was much more personal. It reflected his singular reading regime, and itworked with a certain shorthand: In later years Deutsch often just cited ‘Yiddish papers’or ‘Daily papers’, and in some instances he referred to ‘private information’. The cards,topics, and sources provide a sense of the specific information that interested Deutsch.

Examining the cards, it becomes clear that the index constitutes not a mythic totalhistory but a specific set of facts and data that piqued Deutsch’s interest and whichreflected his personal research priorities (see Figure 2).

Does this mean that the schema is available now since the bug is closed?

Politique documentaire Ensemble des objectifs et processus pilotant la gestion de l’information, incluant la politique d’acquisition, la politique de conservation et la politique de médiation des collections. La politique documentaire est une partie intégrante et essentielle du projet d'établissement, permettant de répondre aux missions de la structure et aux attentes des usagers.

We brought in a metadata librarian, Elizabeth Padilla, from British Columbia Institute of Technology (BCIT), to ensure people can find the materials in the niches they want, using the language they already know.

5.5 Logic, reason, and common sense are your best tools for synthesizing reality and understanding what to do about it.

4.4 Find out what you and others are like.

4.2 Meaningful work and meaningful relationships aren’t just nice things we chose for ourselves—they are genetically programmed into us.

4.1 Understand the power that comes from knowing how you and others are wired.

4 Understand That People Are Wired Very Differently

3.4 Triangulate your view with believable people who are willing to disagree.

25:32 - We have no social constraints anymore

Gandhi once said, “Anything that exists is possible.

No option is perfect here, but a warning seems like a decent compromise unless there's a whole bunch of other plugins that break

Indeed, if MoneySerializer was reloadable, starting with Rails 7 such initializer would raise a NameError.

Hands can be a prompt, a window, a way station—butwhat they ought never have to be is still.

such as installing permanent lighting

I just thought that if there was any time to improve the naming it would be now, before rolling it out to thousands of devs/projects. I don't think of that as bikeshedding, personally.

Comments are turned off.

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.

Okay thank you. I'll need to do some thinking then on how to apply that to things like git config --global core.editor

If you forget to define x in the object you pass as the second argument, or if there's some similar bug or confusion, you won't get an error -- just unexpected results.

Aaron linkt in zijn blogpost aan meer bronnen die ik zeker eens verder wil onderzoeken voor mijn eigen Frankopedia.

Sanity check = Does this even make sense? For example, if your application only outputs integers, sqrt(-1) and log(-1) are undefined.

Sending body/payload in a GET request may cause some existing implementations to reject the request — while not prohibited by the specification, the semantics are undefined. It is better to just avoid sending payloads in GET requests.

However, this request-by-request mindset doesn’t map well to GraphQL because there’s only one controller and the requests that come to it may be very different.

Whether you agree or not, to me there's nothing in this world that is entirely apolitical - when there are people there is politics. You don't have to agree with my views, nor do I expect you to. Diversity and disagreement is what drives mankind forward.

We’ve enabled deprecation warnings by default when running specs. Making these warnings more visible to developers helps upgrading to newer Ruby versions.

DigiNotar was a Dutch certificate authority owned by VASCO Data Security International, Inc.[1][2] On September 3, 2011, after it had become clear that a security breach had resulted in the fraudulent issuing of certificates, the Dutch government took over operational management of DigiNotar's systems.[3]

wanted to surface to the user during SSR if the client-side call would likely fail due to cross-origin fetching, credentials, etc.

First of all, I would start off presenting yourself: Dear XYZ support team I am the web developer in charge of example.com website. By presenting you this way, you are establishing the frame to treat you, hinting that you should be presupposed to be somewhat proficient, so they could choose to answer in a more technical detail.

Feel free to hint, brag, or both! The best CS reps should easily take a hint from clear language and a signature like John Appleseed, JavaScript/Ruby Developer, but any will catch on with a simple line like "I know what I'm doing, so I'd appreciate an extra-technical explanation!"

Hey, I'm a PhD in [field] and do [whatever] professionally. Before calling you, I've narrowed down the problem to [something on their end], so that's what needs to be addressed. If I could speak to an engineer about [specific problem], that'd be great; but if we've gotta walk through the script, let's just knock it out quickly. If they end up requiring the script, then the best way to use your expertise is to run through it quickly. Keep the chit-chat to a minimum and just do the stuff efficiently. If they start describing how to perform some step, you might interrupt them with, "Got it, just a sec.", then let them know once you're ready for the next step.

However, what speaks against just straight up telling them that you're working as [Insert title of your position] and you know what you're talking about?

OP is referring to letting people know they can speak like proper adults when talking about technical terms, without going through the usual nanny-like discourse that tech support has to provide to non-techies. For instance, it happened to me with Amazon support. The speaker told me exactly where to touch in order to clear the cache of the Android Amazon App Store. Given that I work as an app developer the guy could have just said "please clear the cache". No need to go through "tap here, then here, now you should see this, tap that"...

I have tried different tactics of showing the tech support that I am proficient in their field of work (I work as a web developer). Specifically: using accurate terms and technologies to show my knowledge of them and telling the support that I am the "administrator" of the website in question.

How to let tech support subtly know that I am proficient without showing off?

I would argue though that crashing is better than quietly providing unexpected behavior.

We’re the ones who code. The people you talk to are the people who work on your project. When you have a question, we know what we are talking about.

The privacy policy — unlocking the door to your profile information, geodata, camera, and in some cases emails — is so disturbing that it has set off alarms even in the tech world.

Yelp, like Google, makes money by collecting consumer data and reselling it to advertisers.

The good news: everyone had a genuine blast. We knew we had experimented our way into something fun, even if the rules and designs still needed a lot of work.

Svelte is different in that by default most of your code is only going to run once; a console.log('foo') line in a component will only run when that component is first rendered.

click the images below

Software that is not currently being used gradually becomes unusable as the remainder of the application changes.

Infrequently used portions of code, such as document filters or interfaces designed to be used by other programs, may contain bugs that go unnoticed. With changes in user requirements and other external factors, this code may be executed later, thereby exposing the bugs and making the software appear less functional.

As to opinions about the shortcomings of the language itself, or the standard run-times, it’s important to realize that every developer has a different background, different experience, different needs, temperament, values, and a slew of other cultural motivations and concerns — individual opinions will always be largely personal and, to some degree, non-technical in nature.

I don't even know how to tell if they're working 100%, I'm getting mixed signals ..

Should it only contain link* calls?

When should I use link, vs dir, vs. tree?

but I still have no idea if I'm writing this new file correctly.

If you plan on using a gamepad with big picture mode I made a config that works perfectly so check it out.

Yes, but honestly, and no offense intended, but I don't see the harm in these type questions, nor why some people are offended when they are asked. If I owed a website, I wouldn't mind it because it just creates more pages that can be indexed. I see it as helping the website. But, I did look and didn't see a simple answer. Again, no offense is intended. I've just never understood the complaints.

Almet ji dafa tooy.

Here's the last issue where source maps were discussed before the beta release.

Literally, everything in this example can go wrong. Here’s an incomplete list of all possible errors that might occur: Your network might be down, so request won’t happen at all The server might be down The server might be too busy and you will face a timeout The server might require an authentication API endpoint might not exist The user might not exist You might not have enough permissions to view it The server might fail with an internal error while processing your request The server might return an invalid or corrupted response The server might return invalid json, so the parsing will fail And the list goes on and on! There are so maybe potential problems with these three lines of code, that it is easier to say that it only accidentally works. And normally it fails with the exception.

exceptions are not exceptional, they represent expectable problems

Exceptions are not exceptional

I work with crazy geniuses who share many of my opinions (not all, and that’s good).

There is nothing wrong with building your own “service layer”, and many companies have left the Traiblazer track in the past years due to problems they had and that we think we now fixed.

Can't have a steam library without MMX.

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

This article explains why you shouldn't use getters and setters (and when you can use them) and suggests a design methodology that will help you break out of the getter/setter mentality.