Dave Brace davebrace

What forces layout / reflow

All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.

Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.

Element APIs

Getting box metrics

elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent

Foxbox Digital N-Grams Code Challenge

This is a small programming problem to test your technical ability and coding style.

Instructions

Write a simple script to generate a set of n-grams from a string of text. N-grams are a contiguous sequence of n words from a string of text, and have many applications from full-text search indexes to machine learning.

You'll generate a set of every permutation of contiguous n-grams from a string of text, from 1-gram to n-grams where n is the number of words in the string

Example

Create Git Mirror from SVN Repository

This guide will demonstrate how to mirror an SVN into a Git repo. You're the target audience if you're an SVN user, just getting started with Git and need to coax your project team over to Git.

The branching scenario has been simplified for clarity.

References

Sublime Text 2 – Useful Shortcuts (Mac OS X)

General

⌘T	go to file
⌘⌃P	go to project
⌘R	go to methods
⌃G	go to line
⌘KB	toggle side bar
⌘⇧P	command prompt

	#!/usr/bin/env ruby

	require 'base64'
	require 'nokogiri'
	require 'uri'

	def main
	html = Nokogiri::HTML($stdin.read)
	inline_all_images(html)
	inline_all_css(html)

	#!/bin/bash
	# This script will install a Git pre-push hook that prevents force pushing the master/main branch.
	# There are three variants that I have built:
	# - pre-push: prevents force-pushing to master/main.
	# - pre-push-2: prevents force-pushing to master/main depending on the remote (you need to edit the file!).
	# - pre-push-3: prevents any type of pushing to master/main.
	# Set the desired version like this before proceeding:
	# FILE=pre-push

	# Single repo installation:

	httpClient.DefaultRequestHeaders.Authorization =
	new AuthenticationHeaderValue(
	"Basic",
	Convert.ToBase64String(
	System.Text.ASCIIEncoding.ASCII.GetBytes(
	string.Format("{0}:{1}", username, password))));

	Ruby 2.1.0 in Production: known bugs and patches

	Last week, we upgraded the github.com rails app to ruby 2.1.0 in production.
	While testing the new build for rollout, we ran into a number of bugs. Most of
	these have been fixed on trunk already, but I've documented them below to help
	anyone else who might be testing ruby 2.1 in production.

	@naruse I think we should backport these patches to the ruby_2_1 branch and
	release 2.1.1 sooner rather than later, as some of the bugs are quite critical.
	I'm happy to offer any assistance I can to expedite this process.

	# ...

	# Include specific models (exclude the others):
	config.included_models = Dir.new(Rails.root.join('app', 'models')).entries.map{\|entry\| $1.camelize if entry =~ /^(\w+)\.rb$/ }.compact! + ['Doorkeeper::Application', 'Doorkeeper::AccessGrant', 'Doorkeeper::AccessToken']

	# ...

	# xcode-build-bump.sh
	# @desc Auto-increment the build number every time the project is run.
	# @usage
	# 1. Select: your Target in Xcode
	# 2. Select: Build Phases Tab
	# 3. Select: Add Build Phase -> Add Run Script
	# 4. Paste code below in to new "Run Script" section
	# 5. Drag the "Run Script" below "Link Binaries With Libraries"
	# 6. Insure that your starting build number is set to a whole integer and not a float (e.g. 1, not 1.0)