(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
import vinepy | |
def main(): | |
vine = vinepy.API(username='XXXXX@XXXX.XXX', password='XXXXXXXX') | |
#say hello to westboro baptist | |
wbc_id = 984602341204725760 | |
wbc_timeline = vine.get_user_timeline(user_id = wbc_id) | |
post = wbc_timeline[0] |
Command Line
pry -r ./config/app_init_file.rb
- load your app into a pry session (look at the file loaded by config.ru)pry -r ./config/environment.rb
- load your rails into a pry sessionDebugger
#!/usr/bin/env python | |
""" | |
Inject inverting css | |
Usage: | |
inverted_internet | |
""" | |
from libmproxy import controller, proxy | |
import os | |
import sys |
These are half-baked thoughts.
IRC discussion: http://bitcoinstats.com/irc/bitcoin-dev/logs/2012/10/05#l4591669
{ | |
"folders": | |
[ | |
{ | |
"file_exclude_patterns": | |
[ | |
"*.sublime-*" | |
], | |
"folder_exclude_patterns": | |
[ |
-- show running queries (pre 9.2) | |
SELECT procpid, age(clock_timestamp(), query_start), usename, current_query | |
FROM pg_stat_activity | |
WHERE current_query != '<IDLE>' AND current_query NOT ILIKE '%pg_stat_activity%' | |
ORDER BY query_start desc; | |
-- show running queries (9.2) | |
SELECT pid, age(clock_timestamp(), query_start), usename, query | |
FROM pg_stat_activity | |
WHERE query != '<IDLE>' AND query NOT ILIKE '%pg_stat_activity%' |
The Regex Game | |
Avi Bryant | |
This is a game for two programmers, although it's easy to imagine variations for more. | |
It can be played over email, twitter, or IM, but it's easy to imagine a custom web app for it, and I encourage someone to build one. | |
Each player starts by thinking of a regular expression. The players should decide beforehand on dialect and length restrictions (eg, has to be JavaScript-compatible and under 20 characters). | |
They don't reveal the Regex, but if playing over email etc, should send each other a difficult to brute force hash (eg bcrypt) of the Regex for later verification. | |
They do reveal two strings: one which the Regex will match, and one which it will not. |