If anything in this policy does not fit with your own local policy, you should not use dnswl.org for whitelisting or similar purposes.

Even though I commented earlier i have to side with Chris. A ZK is best suited for argumentative and essay like work, not creative one like poetry.Maybe this is something that we need to discuss as a community as hole: it’s seems that a lot of people try to fit their needs to a system that (in my opinion) it’s neither intended or works for those kinds of projects.

Different brain-imaging techniques provide scientists with insight into different aspects of how the human brain functions.

In 1958, she made her television debut opposite Groucho Marx on the game show, “You Bet Your Life.”

What I do care about, though, is that we might start to accept and adopt opinions like “that feature is bad”, or “this sucks”, without ever pausing to question them or explore the feature ourselves.

Morrison Robblee, 25, a middle school teacher in Massachusetts, resigned after facing antisemitic harassment by a 12-year-old student who allegedly made made hateful drawings, including a Hitler sketch, and gave him an insulting note.Courtesy of Morrison Robble

Are protected members/fields really that bad? No. They are way, way worse. As soon as a member is more accessible than private, you are making guarantees to other classes about how that member will behave. Since a field is totally uncontrolled, putting it "out in the wild" opens your class and classes that inherit from or interact with your class to higher bug risk. There is no way to know when a field changes, no way to control who or what changes it. If now, or at some point in the future, any of your code ever depends on a field some certain value, you now have to add validity checks and fallback logic in case it's not the expected value - every place you use it. That's a huge amount of wasted effort when you could've just made it a damn property instead ;) The best way to share information with deriving classes is the read-only property: protected object MyProperty { get; } If you absolutely have to make it read/write, don't. If you really, really have to make it read-write, rethink your design. If you still need it to be read-write, apologize to your colleagues and don't do it again :) A lot of developers believe - and will tell you - that this is overly strict. And it's true that you can get by just fine without being this strict. But taking this approach will help you go from just getting by to remarkably robust software. You'll spend far less time fixing bugs.

I'm not saying never mark methods private. I'm saying the better rule of thumb is to "make methods protected unless there's a good reason not to".

Marking methods protected by default is a mitigation for one of the major issues in modern SW development: failure of imagination.

I can't count the number of times I've been wrong about whether or not there will ever be a need to override a specific method I've written.

The old wisdom "mark it private unless you have a good reason not to" made sense in days when it was written, before open source dominated the developer library space and VCS/dependency mgmt. became hyper collaborative thanks to Github, Maven, etc. Back then there was also money to be made by constraining the way(s) in which a library could be utilized. I spent probably the first 8 or 9 years of my career strictly adhering to this "best practice". Today, I believe it to be bad advice. Sometimes there's a reasonable argument to mark a method private, or a class final but it's exceedingly rare, and even then it's probably not improving anything.

The same day, Menashe licensed 56 pictures through iStockphoto– for about $1 each.

Solution: Store emails with case sensitivity Send emails with case sensitivity Perform internal searches with case insensitivity

Robustness principle suggests that we accept case sensitive emails

ISO 8601 specifies the use of uppercase letter T to separate the date and time. PostgreSQL accepts that format on input, but on output it uses a space rather than T, as shown above. This is for readability and for consistency with RFC 3339 as well as some other database systems.

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.

Although CAN-SPAM hasn't resulted in less spam, the law gives authorities a new tool in the fight against spam, Lochart said. "It's a good thing we have a law, so when we find some of these roaches, we can prosecute them," he said.

Spammers, apparently in response to CAN-SPAM, changed tactics this year, said Andrew Lochart, director of product marketing at Postini. More spammers are using so-called zombie networks -- computers hijacked with Trojan horse programs -- to send spam, and spammers are using increasingly sophisticated directory harvest attacks to spam corporate mail servers, he sai

CAN-SPAM also prohibits private citizens from suing spammers, instead allowing only state attorneys general or Internet service providers to file civil suits

Commtouch found that 80 percent of spam e-mail didn't include valid return e-mail addresses and more than 40 percent contained subject lines that weren't related to the text of the e-mail.

"There's been no reduction in the volume of spam," says Scott Chasin, MX Logic's chief technology officer. "In fact, the exact opposite--our spam rates are actually going up."

Less than 1 percent of spam e-mail sent to U.S. inboxes this month complies with a national antispam law that went into effect January 1, according to two spam filtering vendors.

If the ego is mentally constituted by this dualistic way of thinking, the ego should be able to die without physical death.

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

Approaching this project, I felt committed to writing a story that could stand on its own; a story that achieved the same things I want ANY of my stories to achieve; a story to which the response might be not, “I see what you did there”, but: “I loved this!”

that's a decade off your life

how much does alcohol smoking or marijuana or psychedelics actually affect lifespan

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

Evrone always encourages the developers to work on what they love and contribute back to the software world by writing open-source, that's how Cuprite Ruby driver for Capybara was born.

This document describes a method for signaling a one-click function for the List-Unsubscribe email header field. The need for this arises out of the actuality that mail software sometimes fetches URLs in mail header fields, and thereby accidentally triggers unsubscriptions in the case of the List-Unsubscribe header field.

Imagine what happens when subscribers change activities, interests, or focus. As a result, they may no longer be interested in the products and services you offer. The emails they receive from you are now either ‘marked as read’ in their inbox or simply ignored. They neither click the spam reporting button nor attempt to find the unsubscribe link in the text. They are no longer your customers, but you don’t know it.

In our system, events are generated by physical hosts and follow different routes to the event storage. Therefore, the order in which they appear in the storage and become retrievable - via the events API - does not always correspond to the order in which they occur. Consequently, this system behavior makes straight forward implementation of event polling miss some events. The page of most recent events returned by the events API may not contain all the events that occurred at that time because some of them could still be on their way to the storage engine. When the events arrive and are eventually indexed, they are inserted into the already retrieved pages which could result in the event being missed if the pages are accessed too early (i.e. before all events for the page are available). To ensure that all your events are retrieved and accounted for please implement polling the following way:

partnerships, networking, and revenue generation such as donations, memberships, pay what you want, and crowdfunding

Donations

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.

This buildpack installs shims that always add --headless, --disable-gpu, --no-sandbox, and --remote-debugging-port=9222 to any google-chrome command as you'll have trouble running Chrome on a Heroku dyno otherwise.

Until now, we had a lot of code. Although we were using a plugin to help with boilerplate code, ready endpoints, and webpages for sign in/sign up management, a lot of adaptations were necessary. This is when Doorkeeper comes to the rescue. It is not only an OAuth 2 provider for Rails but also a full OAuth 2 suite for Ruby and related frameworks (Sinatra, Devise, MongoDB, support for JWT, and more).

The answer lies in an important and helpful rule of reading that is generally overlooked.That rule is simply this: In tackling a difficult book for the firsttime, read it through without ever stopping to look up orponder the things you do not understand right away.

Emerson is, “I cannot remember the books I’ve read any more than the meals I have eaten; even so, they have made me.”

Good question! This is going to be a bit long, so bear with me

As to whether you should be using Tini.

Well, actually, some ligatures do have legacy codes, but solely for backwards compatibility with outdated encodings from the long-gone, dark ages of eight-bit computing. E.g. f_f can have the U+FB00 LATIN SMALL LIGATURE FF code point. If ‘eight-bit’ does not tell you anything, please erase everything you read within these parentheses from your memory immediately, keep calm and continue reading.

that's right, we don't want to do params = { ... } because then we're hardcoding the implementation and it becomes very coupled. The benefit of doing it like in my examples is that you can change the method signature and still automatically capture all keyword parameters.

Some people eventually realize that the code quality is important, but they lack of the time to do it. This is the typical situation when you work under pressure or time constrains. It is hard to explain to you boss that you need another week to prepare your code when it is “already working”. So you ship the code anyway because you can not afford to spent one week more.

To see if you are writing good code, you can question yourself. how long it will take to fully transfer this project to another person? If the answer is uff, I don’t know… a few months… your code is like a magic scroll. most people can run it, but no body understand how it works. Strangely, I’ve seen several places where the IT department consist in dark wizards that craft scrolls to magically do things. The less people that understand your scroll, the more powerfully it is. Just like if life were a video game.

So make sure to write your documentation, but do not explain your spells.

This is so clear that you don’t even need comments to explain it.

Another type of comments are the ones trying to explain a spell.

Do not explain your spells, rewrite them.

people usually forgets about one of the greatest advantages of Open Source. YOU can fix the issue. You can download the source code and dig deep into the code allow you to keep moving. Also, you can merge this changes back to the original repository so others doesn’t have to fix it again. win-win relationship.

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

If anyone can completely refactor the JSON Schema description for OpenAPI v3.0 to accurately describe the schema in all its glory, without using this new keyword, then please do so, but I would kindly ask you to test the theory first.

This is a distillation of the results of 230+ comments on #515, not to mention the 300+ comments spread across several other older issues that fed into that one. I know it's long. Please don't complain unless you can offer a shorter write-up. :-)

Booleans and nil can be compared by identity and therefore the `be` matcher is preferable as it is a more strict test.

Just because you can create a plugin for any tool and manage its versions with asdf, does not mean that is the best course of action for that specific tool.

Here are some problems with current issues usage and why we are looking into work items:

Why another tool?: At the moment of writting there exists no proper platform-independent GUI dialog tool which is bomb-proof in it's output and exit code behavior

Adult

5.11 Convert your principles into algorithms and have the computer make decisions alongside you.

4.5 Getting the right people in the right roles in support of your goal is the key to succeeding at whatever you choose to accomplish.

4.4 Find out what you and others are like.

4.3 Understand the great brain battles and how to control them to get what “you” want.

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

3.6 Understand how you can become radically open-minded.

3.5 Recognize the signs of closed-mindedness and open-mindedness that you should watch out for.

2.6 Remember that weaknesses don’t matter if you find solutions.

2 Use the 5-Step Process to Get What You Want Out of Life

The paradox of hoarding isthat no matter how much we collect and accumulate, it’s neverenough.

The intent of this specification and related tools is to expand the reach of development containers, allow the usage of containers by themselves or different orchestration technologies, and allow any tool to manage and create them.

The focus of the dev container specification is to describe how to enrich a container for the purposes of development, rather than acting as a multi-container orchestrator format.

There is something nice about aligning with the platform. But it risks being a straitjacket, and I think we can provide better ergonomics when it comes to streaming.

The last note is that when binding commands to keyboard shortcuts it is often necessary to only have one command, not two commands connected with a pipe like we use above. You can accomplish this by invoking your piped command as a command string argumetn to a new shell like this:

I mean there’s no single answer that will solve all of our future problems. There’s no magic bullet. Instead there are thousands of answers — at least. You can be one of them if you choose to be.'

There are a couple of reasons why you may want to do this.

Why does this even exist ? So you can seperate the data and structure migrations in different folders

Ruby Object Mapper (rom-rb) is a fast ruby persistence library with the goal of providing powerful object mapping capabilities without limiting the full power of the underlying datastore.

If the gem purpose is still not clear please check out this blog post.

Employing theLinked Data paradigm for enterprise data integration has anumber of advantages:

There is nothing stopping you from creating store objects which scrapes XE for the current rates or just returns rand(2):

You can’t take your audience with you.

The power of await is that it lets you write asynchronous code using synchronous language constructs.

Point being (again), definitions seem to differ, and what you call "full stack" is what I call "batteries-included framework". Full stack simply means (for me) that it gives you a way of building frontend and backend code, but implies nothing about what functionality is included in either part.

This is just one of those things in CSS that seems easy to understand (and really, it should be), but it’s sometimes not — because of the way that percentages work in CSS.

The Google Career Certificates Employer Consortium consists of over 150 U.S. companies like Deloitte, Infosys, Snap Inc., Target, Verizon, and of course, Google. These companies span multiple sectors and are committed to considering Google Career Certificate graduates for entry-level jobs. Upon completion of a Google Career Certificate, you will gain access to an exclusive job platform where you can easily apply to opportunities from employers with open jobs. https://grow.google/certificates/it-support/#?modal_active=none

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

From a client side/application (as a whole) standpoint this is an internal endpoint, for the router of SvelteKit this would be an external resource.

I’ve written a few thousand words on why traditional “semantic class names” are the reason CSS is hard to maintain, but the truth is you’re never going to believe me until you actually try it.

If you can suppress the urge to retch long enough to give it a chance, I really think you'll wonder how you ever worked with CSS any other way.

Yeah I don’t think we will find something that works for everyone in all cases. But Webpacker is quite flexible with the setup it has now. Easy to change!

Caution: This is NOT the current local time in most locations in that time zone North America: Only some locations are currently on MST because most places in this time zone are currently on summer time / daylight saving time and are observing MDT.

In everyday usage, MST is often referred to as Mountain Time (MT) or the Mountain Time Zone. This can add a bit of confusion as the term Mountain Time does not differentiate between standard time and Daylight Saving Time, so Mountain Time switches between MST and MDT in areas that use DST during part of the year.

which looks like complete nonsense if you don't really know what's going on

What happens when you look it up in a dictionary rather than as a phrase in Google? Google just catalogues other people's [mis-]uses

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.

I have a rule that I won't allow Capybara to be monkey-patched in Poltergeist. This gives some indication to users about whether something is non-standard. So basically all non-standard stuff must be on page.driver rather than page (or a node).

There is currently no standard for transporting instances of JSON text within a stream protocol

The goal of this technology is to provide a mechanism for browser-based applications that need two-way communication with servers that does not rely on opening multiple HTTP connections (e.g., using XMLHttpRequest or <iframe>s and long polling).

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.

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

Remember that in the end, especially in scripting, there always are more than one way to skin a cat, but some ways are more portable, more reliable, make it simpler to handle error cases, parse the output, etc.

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.

When mocking is deemed profitable:

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?

They have to ask you the dumb questions, either because their employer demands they do, or sometimes because their computer system doesn't let them get to the next part of the script unless they play ball.

Another will employ smart people who apologise to you profusely for having to go through all the pointless steps, but that's just what they have to do!

None of the existing repository filtering tools did what I wanted; they all came up short for my needs. No tool provided any of the first eight traits below I wanted, and all failed to provide at least one of the last four traits as well: