Skip to content

Instantly share code, notes, and snippets.

View tomjadams's full-sized avatar

Tom Adams tomjadams

36 followers · 21 following
View GitHub Profile
@tomjadams
tomjadams / Everesting notes.md
Last active December 17, 2020 20:50

Everesting notes

Floods Road: https://www.strava.com/activities/492911911

Choose a good climb. There's a trade off between getting it done quickly on a steep hill and it being hard; compared to an easy climb and it being longer and taking more time. Choose a climb that suits you, my ideal would be mostly seated with the occasional pinch to give you some standing. Be careful with the descent, late at night it gets hard with wildlife, and if it rains it become extra hard.

If possible, choose somewhere without traffic. Ours had none during the night but was quite busy during the day. This was tricky as it was quite a narrow road.

Invite as many people as you can. Sherpas are awesome and will help you through. Rely on them to roll laps, make food, set up camp, get food, etc. You will make it far far harder for yourself if you try to do it solo.

@tomjadams
tomjadams / ExampleServer.scala
Created June 4, 2016 09:38 — forked from vastdevblog/ExampleServer.scala
Example of a Finagle server
package com.vast.example
import java.net.InetSocketAddress
import java.util.UUID
import java.util.concurrent.{Executors, TimeUnit}
import com.google.common.base.Splitter
import com.twitter.finagle.http.Http
import com.twitter.finagle.builder.{Server, ServerBuilder}
import com.twitter.finagle.service.TimeoutFilter
import com.twitter.finagle.{Service, SimpleFilter, GlobalRequestTimeoutException}
@tomjadams
tomjadams / how-to-set-up-stress-free-ssl-on-os-x.md
Created October 29, 2015 22:44 — forked from jed/how-to-set-up-stress-free-ssl-on-os-x.md
How to set up stress-free SSL on an OS X development machine

How to set up stress-free SSL on an OS X development machine

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

@tomjadams
tomjadams / keybase.md
Created June 3, 2015 05:23

Keybase proof

I hereby claim:

  • I am tomjadams on github.
  • I am tomjadams (https://keybase.io/tomjadams) on keybase.
  • I have a public key whose fingerprint is 7B49 AB1D 852C A251 787A 5979 12C9 3ADB DD07 A6DC

To claim this, I am signing this object:

@tomjadams
tomjadams / gist:a8991752b1787f31e573
Last active August 29, 2015 14:01 — forked from bitemyapp/gist:8739525

This is my recommended path for learning Haskell.

Something to keep in mind: don't sweat the stuff you don't understand immediately. Just keep moving.

Primary course

Installing Haskell

Ubuntu PPA

@tomjadams
tomjadams / gist:1984cc8c10d73032bb32
Created May 8, 2014 07:25 — forked from bitemyapp/gist:8739525

This is my recommended path for learning Haskell.

Something to keep in mind: don't sweat the stuff you don't understand immediately. Just keep moving.

Primary course

Installing Haskell

Ubuntu PPA

@tomjadams
tomjadams / bar.rb
Created April 15, 2014 03:42
foo
(1..2).each { |i| puts i }
@tomjadams
tomjadams / pr.md
Created March 23, 2014 23:26 — forked from piscisaureus/pr.md

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 = git@github.com: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:

@tomjadams
tomjadams / notes.md
Created July 25, 2011 11:36 — forked from nkpart/notes.md
My Lion Install Notes
@tomjadams
tomjadams / functional_journey.md
Created August 17, 2010 11:17 — forked from nkpart/functional_journey.md

Interesting FP Reading

Papers

  • [Why Functional Programming Matters][whyfp]
  • [Applicative Programming with Effects][app]
  • [The Essence of the Iterator Pattern][iter]
  • [Generalising Monads to Arrows][arrows]