Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.
Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.
| class Message < ActiveRecord::Base | |
| scope :last_two_weeks, -> { | |
| where(:created_at => (2.weeks.ago..Time.now)) | |
| } | |
| scope :for_month, (date) -> { | |
| where(:created_at => (date.beginning_of_month..date.end_of_month)) | |
| } | |
| def self.sum_word_count |
| $ = jQuery | |
| queues = {} | |
| running = false | |
| queue = (name) -> | |
| name = 'default' if name is true | |
| queues[name] or= [] | |
| next = (name) -> |
| /** | |
| * `Ember.MergedArray` is an array that observes multiple other arrays (called source arrays) for changes and includes | |
| * all items from all source arrays in an efficient way. | |
| * | |
| * Usage: | |
| * | |
| * ```javascript | |
| * var obj = Ember.Object.create({ | |
| * people: [ | |
| * { |
| #https://gist.github.com/tlowrimore/5162327 | |
| #http://stackoverflow.com/a/15413611/270511 | |
| module ActiveRecord::UnionScope | |
| def self.included(base) | |
| base.send :extend, ClassMethods | |
| end | |
| module ClassMethods | |
| def union_scope(*scopes) |
| #!/usr/bin/env bash | |
| # MIT © Sindre Sorhus - sindresorhus.com | |
| # git hook to run a command after `git pull` or `git checkout` if a specified file was changed | |
| # Run `chmod +x post-checkout` to make it executable then put it into `.git/hooks/`. | |
| changed_files="$(git diff-tree -r --name-only --no-commit-id HEAD@{1} HEAD)" | |
| check_run() { | |
| echo "$changed_files" | grep --quiet "$1" && echo " * changes detected in $1" && echo " * running $2" && eval "$2" |
| (function ($) { | |
| 'use strict'; | |
| /* Based on https://github.com/wikimedia/mediawiki-extensions-NavigationTiming/ */ | |
| function recordTimeToFirstPaint() { | |
| // Use Chrome's loadTimes or IE 9+'s msFirstPaint to record the time to render in milliseconds: | |
| var firstPaintTime, timingSource; | |
| if ('chrome' in window && $.isFunction(window.chrome.loadTimes)) { |
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.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <title>Toggle Switch</title> | |
| <style> | |
| .switch { | |
| position: relative; | |
| } | |
| .switch label { | |
| width: 55px; |
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <title>Customized range slider, pure CSS</title> | |
| <style> | |
| body { | |
| background: #f8f8f8; | |
| } | |
| .slider { | |
| width: 302px; |