IanColdwater

Mute these words in your settings here: https://twitter.com/settings/muted_keywords

ActivityTweet
generic_activity_highlights
generic_activity_momentsbreaking
RankedOrganicTweet
suggest_activity
suggest_activity_feed
suggest_activity_highlights
suggest_activity_tweet

cellularmitosis

import UIKit

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {

    var window: UIWindow?

    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {

        let window = UIWindow(frame: UIScreen.main.bounds)

tclementdev

libdispatch efficiency tips

The libdispatch is one of the most misused API due to the way it was presented to us when it was introduced and for many years after that, and due to the confusing documentation and API. This page is a compilation of important things to know if you're going to use this library. Many references are available at the end of this document pointing to comments from Apple's very own libdispatch maintainer (Pierre Habouzit).

My take-aways are:

• You should create very few, long-lived, well-defined queues. These queues should be seen as execution contexts in your program (gui, background work, ...) that benefit from executing in parallel. An important thing to note is that if these queues are all active at once, you will get as many threads running. In most apps, you probably do not need to create more than 3 or 4 queues.

• Go serial first, and as you find performance bottle necks, measure why, and if concurrency helps, apply with care, always validating under system pressure. Reuse

robwalkerco

var paths = []
var count = 1

// Before running this script, you will need to scroll
// to the bottom of the zenfolio page to ensure all the
// images in the dom
function openAllPhotos() {
  // Collect the paths for each photo
  $('.pv-inner img:first-child').each((index, image) => {
    paths.push(image.style.backgroundImage.split('"')[1])	

yossorion

What I Wish I'd Known About Equity Before Joining A Unicorn

Disclaimer: This piece is written anonymously. The names of a few particular companies are mentioned, but as common examples only.

This is a short write-up on things that I wish I'd known and considered before joining a private company (aka startup, aka unicorn in some cases). I'm not trying to make the case that you should never join a private company, but the power imbalance between founder and employee is extreme, and that potential candidates would

kyle-eshares

from __future__ import unicode_literals

from django.db import models
from django.db.models.fields.related_descriptors import ForwardManyToOneDescriptor  # noqa


class RelationNotLoaded(Exception):
    pass

barneygale

import sys, marshal, functools, subprocess

child_script = """
import marshal, sys, types;
fn, args, kwargs = marshal.load(sys.stdin)
marshal.dump(
    types.FunctionType(fn, globals())(*args, **kwargs),
    sys.stdout)
"""

coltin

cwebp -pass 10 -mt -alpha_filter best -alpha_cleanup -m 6 -lossless

What do all these arguments do?
-pass 10            Determines the number of passes that will be performed on the image, maximum 10. More = longer processing time, but potentially smaller images. Yum.
-mt                 Use multi-threading
-alpha_filter best  "predictive filtering for alpha plane", tries to optimize the alpha channel. Options are none, fast, and best.
-m 6                Determines compression method. 0=fast, 6=slowest
-lossless           Makes this WebP lossless. Image produced will be 100% identical once decompressed.

streeter

"""
Simple web server that listens for Github webhooks to implement push-to-deploy
with Pelican static sites

Settings are loaded from a json file except for SECRET which should be an
environment variable

Example `deployer.json`

{

simonw

How to get Heroku to log full user_agent strings using nginx

Heroku's default logging format omits user agent and referrer strings - but these are useful to have! Especially if you want to be able to run your own analysis on what kind of browsers are using your service.

A default Heroku log line looks like this:

heroku/router:  at=info method=GET path="/page-on-your-site/"

host=your-site.herokuapp.com