| # Custom Keymap for RubyMine (by fxn) | |
| The keymap I work with, inspired by my past Emacs years, these are configurable | |
| in Preferences -> Keymap. | |
| Most of these have no conflict with the existing shortcuts, I use the default | |
| keymap for Mac OS X and add these ones (an action can have several shortcuts). | |
| To configure two strokes enter the first one in the main textfield (eg, C-g), | |
| check "Second Stroke" and the second one there (eg, c). |
| This is the default .slate file. | |
| # If no ~/.slate file exists this is the file that will be used. | |
| config defaultToCurrentScreen true | |
| config nudgePercentOf screenSize | |
| config resizePercentOf screenSize | |
| # General aliases | |
| alias sox screenOriginX | |
| alias soy screenOriginY |
| #!/usr/bin/env ruby | |
| require 'open-uri' | |
| require 'JSON' | |
| require 'digest/sha2' | |
| require 'pry' | |
| require 'bigdecimal' | |
| require 'bitcoin' # Because I need to cheat every now and then | |
| # Usage: | |
| # gem install pry json ffi ruby-bitcoin |
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.
| Surround: | |
| yss" - surround whole line with " | |
| ysiw" - surround a word with " | |
| cs'" - replace surround - with " | |
| ds" - delete surround " | |
| Tabs: |
Prerequisites:
Software components used:
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying
| Installing Arch: | |
| sudo vim /etc/pacman.conf | |
| Update packages list: sudo pacman -Syy | |
| run sudo pacman -Syu before installing any software (to update the repositories first) | |
| * Timing issue: | |
| - Change hardware clock to use UTC time: | |
| sudo timedatectl set-local-rtc 0 |
| ### Last tested February 7 2014 on a Galaxy S3 (d2att) running Cyanogenmod 11 nightly, with Google Authenticator 2.49. | |
| ### Device with Google Authenticator must have root. | |
| ### Computer requires Android Developer Tools and SQLite 3. | |
| ### Connect your device in USB debugging mode. | |
| $ cd /tmp | |
| $ adb root | |
| $ adb pull /data/data/com.google.android.apps.authenticator2/databases/databases |
| require "base64" | |
| require 'openssl' | |
| require 'json' | |
| class CoinbaseExchange | |
| def initialize(key, secret, passphrase) | |
| @key = key | |
| @secret = secret | |
| @passphrase = passphrase | |
| end |
