start new:
tmux
start new with session name:
tmux new -s myname
{ | |
"color_scheme": "Packages/User/textmate-solarized/Solarized (Dark).tmTheme", | |
"default_line_ending": "unix", | |
"dictionary": "Packages/Language - English/en_GB.dic", | |
"draw_white_space": "selection", | |
"find_selected_text": true, | |
"font_face": "menlo", | |
"font_size": 12, | |
"highlight_line": true, |
# Mac OS X Lion introduced a new, iOS-like context menu when you press and hold a key | |
# that enables you to choose a character from a menu of options. If you are on Lion | |
# try it by pressing and holding down 'e' in any app that uses the default NSTextField | |
# for input. | |
# | |
# It's a nice feature and continues the blending of Mac OS X and iOS features. However, | |
# it's a nightmare to deal with in Sublime Text if you're running Vintage (Vim) mode, | |
# as it means you cannot press and hold h/j/k/l to move through your file. You have | |
# to repeatedly press the keys to navigate. |
import mock | |
class AlmostAlwaysTrue(object): | |
def __init__(self, total_iterations=1): | |
self.total_iterations = total_iterations | |
self.current_iteration = 0 | |
def __nonzero__(self): | |
if self.current_iteration < self.total_iterations: |
Forward
I have been using the term "Viking Coder" for a several years now. Honestly, it was a "equal and opposite" reaction to the rise of the Rockstar Ninja Samurai whatever in job descriptions. I don't play a guitar or dress in black PJ's. I am a tall person, and I like big, simple solutions to problems. And I am least a little bit Scandinavian.
I wanted to open this up, so steal, pull, push away!
Thus the Viking Coder was born.
The Viking coder is also a response to many of the Agile practices out there. We mean to strip the nonessential bits of cruft away and expose the naked goodness of what we have learned over the last few decades.
license: gpl-3.0 | |
border: no | |
height: 1060 | |
redirect: https://beta.observablehq.com/@mbostock/d3-radial-tidy-tree |
rsync (Everyone seems to like -z, but it is much slower for me)
(This gist is pretty old; I've written up my current approach to the Pyramid integration on this blog post, but that blog post doesn't go into the transactional management, so you may still find this useful.)
I've created a Pyramid scaffold which integrates Alembic, a migration tool, with the standard SQLAlchemy scaffold. (It also configures the Mako template system, because I prefer Mako.)
I am also using PostgreSQL for my database. PostgreSQL supports nested transactions. This means I can setup the tables at the beginning of the test session, then start a transaction before each test happens and roll it back after the test; in turn, this means my tests operate in the same environment I expect to use in production, but they are also fast.
I based my approach on [sontek's blog post](http://sontek.net/blog/