brian wickman - @wickman
[TOC]
Pants makes the manipulation and distribution of hermetically sealed Python environments
Locate the section for your github remote in the .git/config
file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = [email protected]:joyent/node.git
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/*
to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:
Twitter Flight is great framework for organizing frontend codebase. It make it more productive to work with and easier to test. However, it lacks in support for testing its modules. Moreover, there is not many guidance available on the web yet since it is fairly new.
This post explains how I setted up both in-browser and headless jasmine test for Twitter flight components used in Rails app.
Followings are used for the setup:
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.
// Pop quiz! | |
// 1. What will x and y be in this code? | |
(function() { | |
var x = 5; | |
var y = 10; | |
var coordinates = x, y; | |
console.log('First'); | |
console.log(x); |
#!/bin/sh | |
if [ "master" = "$(git rev-parse --abbrev-ref HEAD)" ] ; then | |
echo "\033[1;31mYou may not shove master\033[0m" | |
exit 1; | |
fi | |
exec git push --force origin HEAD |
(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.