Roll your own iPython Notebook server with Amazon Web Services (EC2) using their Free Tier.
#!/usr/bin/ruby | |
# | |
# This script fixes /usr/local only. | |
# | |
# 6th January 2010: | |
# Modified the script to just fix, rather than install. - rpavlik | |
# | |
# 30th March 2010: | |
# Added a check to make sure user is in the staff group. This was a problem | |
# for me, and I think it was due to me migrating my account over several |
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
-
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the
secure
flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection. -
Use production SSL certificates locally. This is annoying
Find it here: https://github.com/bitemyapp/learnhaskell
http://eloquentjavascript.net/index.html | |
http://eloquentjavascript.net/00_intro.html | |
http://eloquentjavascript.net/01_values.html | |
http://eloquentjavascript.net/02_program_structure.html | |
http://eloquentjavascript.net/03_functions.html | |
http://eloquentjavascript.net/04_data.html | |
http://eloquentjavascript.net/05_higher_order.html | |
http://eloquentjavascript.net/06_object.html | |
http://eloquentjavascript.net/07_elife.html | |
http://eloquentjavascript.net/08_error.html |
@interface UIWindow (resize) | |
-(void)_adjustSizeClassesAndResizeWindowToFrame:(CGRect)frame; | |
@end | |
typedef enum _UICustomRes | |
{ | |
UICustomResiPadTwoThirds, | |
UICustomResiPadHalf, | |
UICustomResiPadOneThird, | |
UICustomResiPhone47, |
int[][] result; | |
float t, c; | |
float ease(float p) { | |
return 3*p*p - 2*p*p*p; | |
} | |
float ease(float p, float g) { | |
if (p < 0.5) | |
return 0.5 * pow(2*p, g); |
This is a collection of snippets, not a comprehensive guide. I suggest you start with Operational PGP.
Here is an incomplete list of things that are different from other approaches:
- I don't use keyservers. Ever.
- Yes, I use Gmail instead of some bespoke hipster freedom service
Interfaces naturally emerge as software gets broken down into parts communicating with one another. The larger and more deliberate structures emerge from a deliberate attempt to organize the development process itself. [fn:Liskov2008] Structure often emerge directly from division of labor: as teams take on independent tasks, interfaces are established betweeen domains they become responsible for. (Conway’s Law)
Software developers are responsible for systems built out of very small atoms while ultimately performing tasks for their users of a much greater magnitude. Dijkstra showed this by computing the ratio between grains of time at the lowest and largest atoms of the system (from say, CPU instructions to a human interaction with the system) The span was already quite large by Dijkstra’s time, of about 10^9. Today this ratio would be at least above 10^12 (see grain ratios)
This large span has to be manage