I hereby claim:
- I am rm-hull on github.
- I am rhu (https://keybase.io/rhu) on keybase.
- I have a public key ASAlyPkfDitTkB4MCdhTjMXTFIdzrBMeS1n4MyUgahQ3VQo
To claim this, I am signing this object:
<?xml version="1.0" encoding="UTF-8"?> | |
<kml xmlns="http://www.opengis.net/kml/2.2"> | |
<Document> | |
<name>Great Yorkshire Bike Ride</name> | |
<description><![CDATA[biking<br><br>Created by Google My Tracks on Android.]]></description> | |
<Style id="icon-ci-1-nodesc-normal"> | |
<IconStyle> | |
<scale>1.1</scale> | |
<Icon> | |
<href>images/icon-1.png</href> |
<?xml version="1.0" encoding="ISO-8859-1"?> | |
<gpx version="1.1" | |
creator="Memory-Map 5.4.2.1089 http://www.memory-map.com" | |
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | |
xmlns="http://www.topografix.com/GPX/1/1" | |
xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd"> | |
<rte> | |
<name>Route213</name> | |
<type>Route</type> | |
<rtept lat="54.2945964162" lon="-1.9830303434"> |
#!/usr/bin/perl | |
# This script is made to show graphs with git commit time made on workweek vs weekend | |
# | |
# The desription of this script and results of its usage is avaliable at: | |
# https://ivan.bessarabov.com/blog/famous-programmers-work-time-part-2-workweek-vs-weekend | |
# | |
# usage: | |
# | |
# git log --author="Sebastian Riedel" --format="%H %ai" | perl script.pl |
I hereby claim:
To claim this, I am signing this object:
// Pixel Spaceships | |
// David Bollinger - July 2006 | |
// http://www.davebollinger.com | |
// for Processing 0115 beta | |
// (updated for 0119 Beta) | |
/** | |
Click mouse to advance early to next pattern<br> | |
*/ |
Original text from http://lists.warhead.org.uk/pipermail/iwe/2005-July/000130.html
From: Mark Jason Dominus <mjd@plover.com>
Date: Jul 28, 2005 11:16 PM
Subject: Re: HOP -vs- SICP
import struct | |
import spidev | |
import sys | |
import time | |
import random | |
import RPi.GPIO as gpio | |
ascii = [ | |
[ 0x55, 0x00, 0x55, 0x00, 0x55 ], | |
[ 0x55, 0x00, 0x55, 0x00, 0x55 ], |
; Based on pp161-176 of "The Magic Machine" by A.K.Dewdney | |
(ns enchilada.palmiters-protozoa | |
(:require | |
[big-bang.core :refer [big-bang]] | |
[big-bang.components :refer [dropdown slider color-picker]] | |
[enchilada :refer [ctx canvas canvas-size proxy-request]] | |
[monet.canvas :refer [circle fill fill-style | |
text text-align | |
stroke-style stroke stroke-width | |
line-to move-to begin-path close-path |
Kris Nuttycombe asks:
I genuinely wish I understood the appeal of unityped languages better. Can someone who really knows both well-typed and unityped explain?
I think the terms well-typed and unityped are a bit of question-begging here (you might as well say good-typed versus bad-typed), so instead I will say statically-typed and dynamically-typed.
I'm going to approach this article using Scala to stand-in for static typing and Python for dynamic typing. I feel like I am credibly proficient both languages: I don't currently write a lot of Python, but I still have affection for the language, and have probably written hundreds of thousands of lines of Python code over the years.
(ns enchilada.wireframe-extrusion | |
(:require | |
[enchilada :refer [canvas ctx value-of canvas-size]] | |
[wireframes.renderer.canvas :refer [draw-solid ->canvas]] | |
[wireframes.renderer.color :refer [wireframe solid]] | |
[wireframes.transform :refer [point combine rotate scale translate degrees->radians]] | |
[wireframes.shapes.primitives :refer [extrude make-line make-point transform-shape center-at-origin]] | |
[jayq.core :refer [show]] | |
[inkspot.color :refer [coerce]] | |
[monet.canvas :refer [get-context fill-rect fill-style]] |