Using Boolean Search on LinkedInLast updated: July 6, 2018You can run a Boolean search on LinkedIn by combining keywords with operators like AND, NOT, and OR during your search.Here are some ways to use Boolean logic and construct your searches: Quoted searches: For an exact phrase, enclose the phrase in quotation marks. For example, type "product manager". You can also use quotation marks if you want to find someone with a multi-word title. LinkedIn search only supports standard, straight quotation marks ("). Other software or websites may use special symbols that our system does not recognize. Curly quotation marks (“), also known as smart quotes or typographer's quotes, aren't supported. In order to optimize overall site performance, stop words such as "by", "in", "with", etc. aren't used. NOT searches: Type the word NOT (capital letters) immediately before a search term to exclude it from your search results. This typically limits your search results. For example, "programmer NOT manager". OR searches: Type the word OR (capital letters) to see results that include one or more items in a list. This typically broadens your search results. For example, "sales OR marketing OR advertising”. AND searches: AND searches: Type the word AND (capital letters) to see results that include all items in a list. This typically limits your search results. For example, "accountant AND finance AND CPA".. Note: You don't need to use AND. If your search has two or more terms, you'll automatically see results that include all of them. Parenthetical searches - To do a complex search, you can combine terms using parentheses. For example, to find people who have "VP" in their profiles, but exclude "assistant to VP" or SVPs, type VP NOT (assistant OR SVP). When handling searches, the overall order to precedence is: Quotes [""] Parentheses [()] NOT AND OR Important: The + and - operators are not officially supported by LinkedIn. Using AND in place of + and NOT in place of - makes a query much easier to read and guarantees that we'll handle the search correctly. When using NOT, AND, or OR operators, you must type them in uppercase letters. We don't support wildcard "*" searches. Boolean search will work in the keyword field in Recruiter and Linkedin.com, and will work in the Company, title, and keyword field in Sales Navigator.

U.S. Senate Subcommittee on Communications, Technology, Innovation, and the Internet, "Optimizing for Engagement: Understanding the Use of Persuasive Technology on Internet Platforms," 25 June 2019, www.commerce.senate.gov/2019/6/optimizing-for-engagement-understanding-the-use-of-persuasive-technology-on-internet-platforms.

Francis Fukuyama et al., Middleware for Dominant Digital Platforms: A Technological Solution to a Threat to Democracy, Stanford Cyber Policy Center, 3, https://fsi-live.s3.us-west-1.amazonaws.com/s3fs-public/cpc-middleware_ff_v2.pdf.

One of those professors recommended I read How to Write a Thesis by Umberto Eco, which I found to be a surprisingly close analog to Luhmann’s Zettelkasten.

Finally, Real America has a strong nationalist character. Its attitude toward the rest of the world is isolationist, hostile to humanitarianism and international engagement, but ready to respond aggressively to any incursion against national interests.

John Peel Sessions

Diels, H. and W. Kranz, Die Fragmente der Vorsokratiker. Zürich/Hildesheim 1964 The standard collection of the texts of and the doxography on Anaximander and the other presocratics.

that's why I bolded "same column" with the or query. I can delete the comment altogether, but thought it would be helpful for people perusing "or" query SO questions.

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).

When an endpoint is to interpret a byte stream as UTF-8 but finds that the byte stream is not, in fact, a valid UTF-8 stream, that endpoint MUST _Fail the WebSocket Connection_. This rule applies both during the opening handshake and during subsequent data exchange.

As Astra Taylor explains in her vital book !e People’sPlatform, this process has often been celebrated by advocates ofnew platforms.

Crenshaw and her classmates asked 12 scholars of color to come to campus and lead discussions about Bell’s book Race, Racism, and American Law. With that, critical race theory began in earnest.

By looking at the code screenshot, you are either opening your mouth in awe or in appall. I feel there is no in-between here.

This works nicely wherever we show authors, but after we deploy to production, the folks from other parts of the world won’t get notified anymore about their songs. Mistakes like these are easy to make when using concerns.

was due to a form that was submitted (ALWAYS SET THAT TYPE-PROPERTY ON YOUR BUTTONS!) after my onclick-event fired, but before my request had any chance to be completed.

(The null result should not be confused with a SQL NULL; see the examples.)

+1 to counter the drive-by downvote. I'd still use sed for this, unless you need the power of Perl regular expressions to select the delimiting lines

I think that it's nonsense not to have a method that just gives -1 or +1. Even BASIC has such a function SGN(n). Why should we have to deal with Strings when it's numbers we want to work with. But's that's just MHO.

That's it! Just replace let! with let_it_be. That's equal to the before_all approach but requires less refactoring.

(Not a Boolean attribute!)

Blogging about your work hits both of those marks. It also means that you have to translate your work from academese to language that non-academics will understand (i.e. jargon) and also foreground the relevance of your work. You have to tell people why your work is important and what it adds to the world.

John Bowers, Elaine Sedenberg, and I have described how that might work, suggesting that libraries can again serve as semi-closed archives of both public and private censorial actions online. We can build what the Germans used to call a giftschrank, a “poison cabinet” containing dangerous works that nonetheless should be preserved and accessible in certain circumstances. (Art imitates life: There is a “restricted section” in Harry Potter’s universe, and an aptly named “poison room” in the television adaptation of The Magicians.)

Transition teams from Mailchimp to Marketo

The relationship between Phillips — one of whose most famous works is A Humument, an ongoing-for-decades collage/manipulation/adaptation of a Victorian book — and Eno is a fascinating one in the history of aleatory or, as I prefer, emergent art.

This is especially nice for opening Vim from other tools, as this call can be done on the command-line: "+call cursor($LINE,$COLUMN)"

Apologies for digging up a closed thread, but it already contains some monorepo examples so feels like the best place to do it.

Ok I'll reopen until the culprit is found

But if you're working on a bigger project, with multiple packages and a complex dependency tree, you might want to combine npm with a tool like Lerna.

npm install <folder>: Install the package in the directory as a symlink in the current project. Its dependencies will be installed before it's linked. If <folder> sits inside the root of your project, its dependencies may be hoisted to the top-level node_modules as they would for other types of dependencies.

The local package will be copied to the prefix (./node-modules).

Israel

eduardo galliano called in defense of the word

Different ways to prepend a line: (echo 'line to prepend';cat file)|sponge file sed -i '1iline to prepend' file # GNU sed -i '' $'1i\\\nline to prepend\n' file # BSD printf %s\\n 0a 'line to prepend' . w|ed -s file perl -pi -e 'print"line to prepend\n"if$.==1' file

Oversharing. Crying, disclosing intimate details, and telling long (unrelated and/or unsolicited) stories about one’s personal life may indicate the lack of an essential social work skill: personal boundaries.

Note that & is a line terminator like ; (write command& not command&;).

You particular circumstances may or may not warrant a way different from what lhunath (and other users) deem "best practices".

The first argument to shared_context (the shared group name) is superfluous. It feels a bit like "what's this argument for again?" (Note that you could still use it with include_context to include the group manually, but it's a bit odd to mix-and-match the approaches).

This kind of error handling does express error state (either via HTTP 500 or by the top-level "errors" key), but it doesn’t take advantage of GraphQL’s type system and can only express one error at a time.

(Always call super to inherit the default behavior.)

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.

Can you provide details of what you mean by "not working as expected"?

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.

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.

In the context of git, the word "master" is not used in the same way as "master/slave". I've never known about branches referred to as "slaves" or anything similar.

"Both Conservancy and the Git project are aware that the initial branch name, 'master,' is offensive to some people and we empathize with those hurt by the use of that term," said the Software Freedom Conservancy.

We should think about the number of simultaneous connections (peak and average) and the message rate/payload size. I think, the threshold to start thinking about AnyCable (instead of just Action Cable) is somewhere between 500 and 1000 connections on average or 5k-10k during peak hours.

Thus, by adding system tests, we increase the maintenance costs for development and CI environments and introduce potential points of failures or instability: due to the complex setup, flakiness is the most common problem with end-to-end testing. And most of this flakiness comes from communication with a browser.

This is why for a recent Angular+Rails project we chose to use a testing stack from the backend technology’s ecosystem for e2e testing.

There are times to stretch individually and as a team, but there are also times to take advantage of what you already know.

When it came to testing the whole product, end-to-end, owning both sides gave us not only more options to consider, but also more tools to choose from.

This meant that we owned both sides of the product implementation. For unit testing on the frontend, we stayed with Angular’s suggestion of Jasmine. For unit testing on the backend, we went with rspec-rails. These worked well since unit tests don’t need to cross technology boundaries.

We used testing tools that were in the same ecosystem as our backend technology stack for primrily three reasons: We owned both ends of the stack Team experience Interacting with the database

We chose to define the frontend in one technology stack (Angular+TypeScript/JavaScript) and the backend in another (Ruby+Ruby on Rails), but both came together to fulfill a singular product vision.

​La forme de cet écrit est multisupport : à l’écran et imprimée, mettant en action les outils développés par les designers que j’étudie dans cette réflexion. Et, le propos sur l’édition à plusieurs est actionné par les commentaires de chaque lecteur disponibles sur la version numérique.

Once a variable is specified with the use method, access it with EnvSetting.my_var Or you can still use the Hash syntax if you prefer it: EnvSetting["MY_VAR"]

Configuration style is exactly the same for env_bang and env_setting, only that there's no "ENV!" method... just the normal class: EnvSetting that is called and configured.