For more information about Nix, please, read Domen's introduction to Nix package manager.
Usage:
$ nix-env -i -f default.nix
$ instance fg
#!/bin/bash | |
# | |
# Wrapper script for trello cli that appends default arguments as well as reads | |
# additional arguments from a file if it exists in the cwd. It is assumed | |
# the file contains a text string of arguments to append to the command. | |
# | |
# See https://github.com/brettweavnet/trello_cli/issues/22 for more details | |
# | |
# For example, the file .trellocli existing in a directory with the content: | |
# |
For more information about Nix, please, read Domen's introduction to Nix package manager.
Usage:
$ nix-env -i -f default.nix
$ instance fg
“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important
or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”
You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?
This is where any fun you might have been having ends. Now it’s time to get serious and talk about rules.
Writing CSS is hard. Even if you know all the intricacies of position and float and overflow and z-index, it’s easy to end up with spaghetti code where you need inline styles, !important rules, unused cruft, and general confusion. This guide provides some architecture for writing CSS so it stays clean and ma
<? | |
///////////////////// | |
// slack2html | |
// by @levelsio | |
///////////////////// | |
// | |
///////////////////// | |
// WHAT DOES THIS DO? | |
///////////////////// | |
// |
* OpenHatch - https://openhatch.org/search/?q=&language=Python | |
* PyLadies - https://github.com/pyladies | |
* New Coder - https://github.com/econchick/new-coder | |
* Django Girls - https://github.com/DjangoGirls | |
* Matplotlib - https://github.com/matplotlib/matplotlib | |
* Hylang - http://docs.hylang.org/en/latest/, https://github.com/hylang/hy | |
* Open Slides (Django) - http://openslides.org/ | |
* Zeeguu - https://zeeguu.unibe.ch | |
* Project Jupyter - https://github.com/jupyter | |
* nbgrader - https://github.com/jupyter/nbgrader |
When you're developing in Node.js, you're likely to run into these terms - "monolithic" and "modular". They're usually used to describe the different types of frameworks and libraries; not just HTTP frameworks, but modules in general.
In software development, the terms "tightly coupled" and "loosely coupled" are used to indicate how much components rely on each other; or more specifically, how many assumptions they make about each other. This directly translates to how easy it is to repla
from abc import ABC, ABCMeta, abstractmethod | |
from collections import namedtuple | |
from itertools import count | |
PayloadFactory = namedtuple('PayloadFactory', [ | |
'good', 'created', 'queued', 'unchanged', 'requires_auth', | |
'permission_denied', 'not_found', 'invalid', 'error' | |
]) | |
""" |
#!/system/bin/sh | |
# What is this? | |
# PSD (Pin to the SD card), is an auxiliary script that keeps your Apps "staying" on your SD card. | |
# "staying" is quoted because what it actually do is moving your app back to the SD card again after an update. | |
# Why? | |
# a. Since Android Lollipop, the apps you moved to the SD card will back to internal storage after an update. | |
# b. My phone has a small internal storage and running Android Lollipop. | |
# c. I am not going to buy another phone or downgrade to Kitkat. |
Taught by Brad Knox at the MIT Media Lab in 2014. Course website. Lecture and visiting speaker notes.
apt update && apt upgrade | |
apt install python python-dev pip clang | |
pip install --upgrade pip | |
pip install conda | |
## All the following packages are needed by conda | |
pip install auxlib ruamel.yaml requests | |
## Install pycosat (this can be ignored if https://github.com/ContinuumIO/pycosat/pull/29 is fixed) | |
wget https://pypi.python.org/packages/76/0f/16edae7bc75b79376f2c260b7a459829785f08e463ecf74a8ccdef62dd4a/pycosat-0.6.1.tar.gz#md5=c1fc35b17865f5f992595ae0362f9f9f | |
tar -xf pycosat-0.6.1.tar.gz |