Adhere to the team’s consensus-based process, but use just barely enough process. We should be aided by our tools and processes, not captive to them—it’s part of our job as a team to help find the right balance.

Automatic unsubscribe footerIn Sending Defaults, select Add Unsubscribe Footer to automatically add the footer to your emails. This setting will apply globally, but if you’d rather include it conditionally, use the rules engine. The footer includes information about the address the email was sent to, along with an unsubscribe link. You do not need a website to process these unsubscribes—Mailchimp will direct the recipient to an unbranded web page confirming that the recipient address has been unsubscribed.

it is suggested that editors print as many articles as possible

Write clean code with minimal cleverness Comprehensibility and resilience far outweigh cleverness. Arcane solutions are not a badge of honor, and understanding your code shouldn’t be a hazing ritual. Don’t be afraid to be boring. New problems do not typically require new technology, nor new architectures. Consistent code helps us ship quickly and sensibly: common conventions and patterns speed everyone up. Experienced team members can understand and extend such code with greater ease, and new developers can get up to speed in a project faster.

1. Ship quickly, but sustainably Ship useful stuff to our users frequently, but responsibly, by way of small iterations and resilient conventions. Keep your changes small Small pull requests (PRs) lead to stronger code, faster iteration, sustainable velocity and a happier team. Smaller PRs with well-structured commits are a kindness to your reviewers, who benefit from a lighter context-switching demand. Code review cycles are speedier and of higher quality: reviewers are able to evaluate the entire change, quickly, without undue cognitive fatigue or LGTM-overwhelm. Smaller changes sharpen your focus, encouraging modular code with a purity of purpose. This in turn elicits clear code organization and can make coding and test-writing faster. Iterate, deploy, repeat Frequently ship iterative changes, using a reliable and non-intimidating deployment mechanism. Smaller releases make it easier to pinpoint a problem should something go awry, and are more straightforward to verify in our QA step. Deploying more often gets features and fixes to users fast, and avoids making giant leaps in (potentially) the wrong direction.

Review with care and humanity Code reviews are business-critical—all production code requires review—and an important opportunity to support your teammates. Everyone involved, whether author or reviewer, has one core objective: help to move things forward. As a reviewer, you are a partner in the success of the body of work. Make code reviews a top priority, and be thorough and compassionate. Commit yourself when you review: focus and take your time. Avoid dismissive terms like “simply”, “just.” Ask questions. Discuss the code, not the coder. There are many conventions and techniques at play in high-quality code reviews, but all involve common underpinnings: be responsive, be committed and be kind. If you’re the code author, set your reviewer up for the best possible review cycle. Roll out the red carpet with a polished PR description. Do everything you can so that your reviewer can get down to the work of reviewing without fuss. Screenshots. Testing instructions. Comments to help them navigate. Remember to expect feedback—that’s the whole point—and to respond to it with the same humanity you expect from your reviewer.

Don’t be a back-seat coder This means holding off, and not requesting many of the code changes that you may be tempted to request. Feedback that asks for too many changes and feels like a rewrite can be demoralizing, so consider your suggestions carefully and pick the best ones. Yes, one of the aims of code review is to find and correct bugs and design issues with the code. But don’t use code review to try to get the author to rewrite the code to the way you would have written it yourself. Remember that many things in software are a matter of opinion, multiple solutions that each have their pros and cons. For each “correction” that you want to suggest ask yourself whether it might be just a difference of opinion? In cases where the author has considered different solutions and chosen one solution for a reason, consider empowering the coder and respecting their right to make that decision.

Hypothesis to choose from:

LTI + API Approach

Create an assignment in CanvasChoose “External Tool” as the Submission TypeChoose the tool from the list that appears in the modalA properly configured tool allows the instructor to then choose a resourceTool returns a content item message to Canvas with the Launch URL to that resourceTeacher saves and publishes the assignment

OAuth 2.0 offers little to none code re-usability.

Return values of methods are still unspecified MagicMocks. For example the code won’t crash in the tests if it tries to call a method that doesn’t exist on the return value of an autospec’d mock’s method: >>> class Foo(object): ... def some_method(): ... return 23 ... >>> mock_foo = mock.create_autospec(Foo, spec_set=True, instance=True) >>> mock_foo.some_method() <MagicMock name='mock.some_method()' id='139778195517520'> >>> >>> # This should crassh but doesn't: >>> mock_foo.some_method().method_that_does_not_exist() <MagicMock name='mock.some_method().method_that_does_not_exist()' id='139778195121168'> Tests can fix this by specifying the return value: >>> mock_foo.some_method.return_value = 23 >>> mock_foo.some_method() 23 >>> mock_foo.some_method().method_that_does_not_exist() Traceback (most recent call last): ... AttributeError: 'int' object has no attribute 'method_that_does_not_exist' But now some duplication between the tests and Foo has been introduced. Again, if the real Foo.some_method() is changed then the above mock code would also need to be updated otherwise the tests for the code that uses Foo could still be passing even though the code is now wrong.

Return values of methods are still unspecified MagicMocks. For example the code won’t crash in the tests if it tries to call a method that doesn’t exist on the return value of an autospec’d mock’s method: >>> class Foo(object): ... def some_method(): ... return 23 ... >>> mock_foo = mock.create_autospec(Foo, spec_set=True, instance=True) >>> mock_foo.some_method() <MagicMock name='mock.some_method()' id='139778195517520'> >>> >>> # This should crassh but doesn't: >>> mock_foo.some_method().method_that_does_not_exist() <MagicMock name='mock.some_method().method_that_does_not_exist()' id='139778195121168'> Tests can fix this by specifying the return value: >>> mock_foo.some_method.return_value = 23 >>> mock_foo.some_method() 23 >>> mock_foo.some_method().method_that_does_not_exist() Traceback (most recent call last): ... AttributeError: 'int' object has no attribute 'method_that_does_not_exist' But now some duplication between the tests and Foo has been introduced. Again, if the real Foo.some_method() is changed then the above mock code would also need to be updated otherwise the tests for the code that uses Foo could still be passing even though the code is now wrong.

Don't compare boolean values to True or False using ==. Yes: if greeting: No: if greeting == True: Worse: if greeting is True:

Note: The mock library actually has two very similar classes - Mock and MagicMock. The difference is that MagicMock supports Python’s magic methods whereas Mock doesn’t. This usually isn’t important, but as the mock user guide says it’s sensible to use MagicMock by default. The Hypothesis tests tend to use Mock more often, though.

PostgreSQL 9.6.4 DocumentationTh

"My Happiness" was released as a single with "My Kind of Scene" as a B-side.

y American author Stephen Crane (1871–1900). The story takes place in the small, fictional town of Whilomville, New York. An African-American coachman named Henry Johnson, who is employed by the town's physician, Dr. Trescott, becomes horribly disfigured after he saves Trescott's son from a fire. When Henry is branded a "monster" by the town's residents, Trescott vows to shelter and care for him, resulting in h

The Jersey Act was introduced to prevent the registration of most American-bred Thoroughbred horses in the British General Stud Book. It had its roots in the desire of the British to halt the influx of American-bred racehorses of possibly impure bloodlines during the early 20th century. Many American-bred horses were exported to Europe to race and retire to a breeding career after a number of US states banned gambling, which depressed Thoroughbred racing as well as breeding in the United States. The loss of breeding records during the American Civil War and the late beginning of the registration of American Thoroughbreds led many in the British racing establishment to doubt t

How could we support “load more” in such situations?

group:K1p4yo

The URL fragment also contains the domain of the annotation service, hypothes.is, as a namespacing element.

Nautilus Type-Ahead Find Feature Enabled By Default In Ubuntu 14.04

gsettings set org.gnome.nautilus.preferences enable-interactive-search false

[New Requirement: When there's activity for you somewhere, indicate it?]

.then((res) => {

window.fetch('/api/v1/users')

Testing API requests from window.fetch

Sec-WebSocket-Key: dGhlIHNhbXBsZSBub25jZQ==

1.6. Security Model

Sec-WebSocket-Accept: s3pPLMBiTxaQ9kYGzzhZRbK+xOo=

If the server does not wish to accept connections from this origin, it can choose to reject the connection by sending an appropriate HTTP error code

The server is informed of the script origin generating the WebSocket connection request.

hypothesis.js

app: jQuery('link[type="application/annotator+html"]').attr('href'),

window.annotator = new Klass(document.body, options);

Annotator.noConflict().$.noConflict(true);

layout.app_inject_urls

var baseUrl = document.createElement('link'); baseUrl.rel = 'sidebar'; baseUrl.href = '{{ app_uri or request.resource_url(context, 'app.html') }}'; baseUrl.type = 'application/annotator+html'; document.head.appendChild(baseUrl);

if (resources.length) { var url = resources.shift(); var ext = url.split('?')[0].split('.').pop(); var fn = (ext === 'css' ? injectStylesheet : injectScript); fn(url, next); }

var injectScript = inject.script || function injectScript(src, fn) {

var injectStylesheet = inject.stylesheet || function injectStylesheet(href, fn) {

embed.js

app.appendTo(@frame)

app = $('<iframe></iframe>') .attr('name', 'hyp_sidebar_frame') .attr('seamless', '') .attr('src', src)

embed = document.createElement('script'); embed.setAttribute('src', embedUrl); document.body.appendChild(embed);

var embedUrl = '{{request.resource_url(context, "embed.js")}}';

bookmarklet.js

Angular Style Guide: A starting point for Angular development teams to provide consistency through good practices.

A Vim plugin for visually displaying indent levels in code

def create_api(global_config, **settings):

return config.make_wsgi_app()

if config.registry.feature('accounts'):

config.include('.features')

config.set_root_factory('h.resources.create_root')

config = Configurator(settings=settings)

def create_app(global_config, **settings):

"""The main h application."""