-
Download an export of your board, rename it to
board.json, and place it in the same directory as this README. For example:https://trello.com/board/4f19b3693754fb034106c89d/welcome-board.json
-
Run trello2todotxt
L1 cache reference ......................... 0.5 ns
Branch mispredict ............................ 5 ns
L2 cache reference ........................... 7 ns
Mutex lock/unlock ........................... 25 ns
Main memory reference ...................... 100 ns
Compress 1K bytes with Zippy ............. 3,000 ns = 3 µs
Send 2K bytes over 1 Gbps network ....... 20,000 ns = 20 µs
SSD random read ........................ 150,000 ns = 150 µs
Read 1 MB sequentially from memory ..... 250,000 ns = 250 µs
| <VirtualHost *> | |
| ServerName example.com | |
| WSGIDaemonProcess www user=max group=max threads=5 | |
| WSGIScriptAlias / /home/max/Projekte/flask-upload/flask-upload.wsgi | |
| <Directory /home/max/Projekte/flask-upload> | |
| WSGIProcessGroup www | |
| WSGIApplicationGroup %{GLOBAL} | |
| Order deny,allow |
| from fabric.api import * | |
| from fabric.contrib.console import confirm | |
| import tempfile | |
| import re | |
| PROJ_VER='4.8.0' | |
| GEOS_VER='3.3.3' | |
| GDAL_VER='1.9.0' | |
| PROJ_PATH='/usr/local/proj/' + PROJ_VER |
This document lays out some baseline expectations between conference speakers and conference presenters. The general goal is to maximize the value the conference provides to its attendees and community and to let speakers know what they might reasonably expect from a conference.
We believe that all speakers should reasonably expect these things, not just speakers who are known to draw large crowds, because no one is a rockstar but more people should have the chance to be one. We believe that conferences are better -- and, dare we say, more diverse -- when the people speaking are not just the people who can afford to get themselves there, either because their company paid or they foot the bill themselves. Basically, this isn't a rock show rider, it's some ideas that should help get the voices of lesser known folks heard.
These expectations should serve as a starting point for discussion between speaker and organizer. They are not a list of demands; they are a list of rea
Here is an essay version of my class notes from Class 1 of CS183: Startup. Errors and omissions are my own. Credit for good stuff is Peter’s entirely.
CS183: Startup—Notes Essay—The Challenge of the Future
Purpose and Preamble
No matter what, you're going to have to learn most everything on your own anyway. Self-learning is hard. Regardless of where, when or how you learn - being a good self-learner will maximize your potential.
In this post, Hamilton Ulmer (an almost-done Stanford stats masters student) and I, will explore seven ways to become a great self-learner.
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:
| # Example of downloading all data from a GeoServer WFS server | |
| # and loading it into a PostGIS database. Use with caution | |
| # as you could put a lot of load on someone's server if they | |
| # host a lot of data which might make them sad. | |
| # In response to: http://underdark.wordpress.com/2012/09/26/wfs-to-postgis-in-3-steps/ | |
| BASEURL="http://data.wien.gv.at/daten/geoserver/ows?service=WFS&version=1.1.0" | |
| for LAYERNAME in `wget -qO- $BASEURL"&request=GetCapabilities" | xpath -q -e "//FeatureType/Name/text()"` ; do | |
| PARTS=(${LAYERNAME//:/ }) |
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <title>My Chart</title> | |
| <meta charset="utf-8"> | |
| </head> | |
| <body> | |
| <p class="my-chart" style="text-align:center"></p> |