Neil de Carteret n3dst4

View api_blueprint_notes.md

API Blueprint

Start with:

FORMAT: 1A
View go_tour_24.go
1 2 3 4 5 6 7 8 9 10
package main
 
import (
"fmt"
"math"
)
 
func Sqrt(x float64) (float64, int) {
last := 0.0
z := 1.0
View pathshrink.sh
1 2 3 4 5 6 7 8 9 10
#!/bin/bash
 
# set this to the problem folder
BASE=/c/Users/ndc/Dropbox/projects/delete-me
 
cd $BASE
for i in `find $BASE -depth`
do
DIR=`dirname $i`
FILE=`basename $i`
View no_caching.cs
1 2 3 4 5
Response.Cache.SetExpires(DateTime.UtcNow.AddDays(-1));
Response.Cache.SetValidUntilExpires(false);
Response.Cache.SetRevalidation(HttpCacheRevalidation.AllCaches);
Response.Cache.SetCacheability(HttpCacheability.NoCache);
Response.Cache.SetNoStore();
View gist:6621406
1 2 3 4 5 6 7 8 9 10
{
// ...
Competition: '',
Participants: [
{
Name: "Manchester United",
Players: [
{
Name: "Fred Fredfredfred",
ShortName: "Fred",
View co-contra-variance.cs
1 2 3 4 5 6 7 8 9
 
// generic type:
public class Bag<T> {}
 
// simple usage:
Bag<Fruit> myBag;
myBag = new Bag<Fruit>();
 
// so far so good
View git_pretty
1
git config --global --add alias.pretty "log --oneline --abbrev-commit --branches=* --graph --decorate"
View web_config_ie_edge.xml
1 2 3 4 5 6 7 8 9 10
<!--
It's all about "forcing" with MS stuff. *Force* IIS to serve a header which will
*force* IE not to use it's shitty compatibility mode, even if it's an intranet
site and the client has "display intranet sites in compatibility view" ticked in
their compatibility prefs.
 
The alternative is to include the equivalent <meta http-equiv...> in your
markup, but that will sometimes be ignored.
 
This header is discouraged by MS for production environments. Then again, MS is
View gist:5183703
1 2 3 4
n3dst4@lesster2:~/438231 (master) $ date; w
Sun Mar 17 17:05:27 EDT 2013
17:09:52 up 4:18, 0 users, load average: 139.84, 120.85, 91.34
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
View gist:3979599
1 2 3 4 5 6 7 8 9 10
-->
POST /tasks/autofiller/101
 
{
object: {
id: 101,
description: 123,
building: 234,
site: 345,
reporter: 456
Something went wrong with that request. Please try again.