| http://museum-api.pbworks.com/w/page/21933420/Museum%C2%A0APIs | |
| http://americanart.si.edu/collections/search/lod/about/ | |
| https://datahub.io/dataset?tags=museum | |
| http://blog.variousbits.net/2009/04/16/the-brooklyn-museum-api-qa-with-shelley-bernstein-and-paul-beaudoin/ | |
| https://medium.com/@andrea_ledesma/how-we-learned-to-stop-worrying-and-love-open-data-a-case-study-in-the-harvard-art-museums-api-893c3f40ecb7#.hthquwry8 | |
| http://labs.cooperhewitt.org/2014/the-api-at-the-center-of-the-museum/ | |
| https://github.com/WaltersArtMuseum/walters-api | |
| http://mw2015.museumsandtheweb.com/paper/art-data-building-the-sfmoma-collection-api/ | |
| http://data.culturehack.org.uk/ | |
| https://www.brooklynmuseum.org/opencollection/api/ |
Disclaimer: This piece is written anonymously. The names of a few particular companies are mentioned, but as common examples only.
This is a short write-up on things that I wish I'd known and considered before joining a private company (aka startup, aka unicorn in some cases). I'm not trying to make the case that you should never join a private company, but the power imbalance between founder and employee is extreme, and that potential candidates would
| alias csvrowcount='for i in `find . -name "*.csv"`; do echo "$i"; csvstat --count $i; done' | |
| alias csvfilecount='find . -name "*.csv" | wc -l' |
| # This shows a bit of shell muscle power | |
| # First, we call find with maxdepth 1. This will make it so that find | |
| # only searches within this current directory | |
| # Then we use -type f to make sure find is only getting files | |
| # then we use \! -name 'config.json'. | |
| # Together, these flags mean that we will get only | |
| # files (not directories, etc.) that are not named `config.json` | |
| # in this directory. | |
| # Thanks to Ike Levy for helping me figure out this badassery |
| ///////////////////////////////////////////////////////// | |
| // Copied from http://www.alecjacobson.com/weblog/?p=3816 | |
| ///////////////////////////////////////////////////////// | |
| #import <Foundation/Foundation.h> | |
| #import <Cocoa/Cocoa.h> | |
| #import <unistd.h> | |
| BOOL copy_to_clipboard(NSString *path) | |
| { | |
| // http://stackoverflow.com/questions/2681630/how-to-read-png-image-to-nsimage | |
| NSImage * image; |
| { | |
| "cells": [ | |
| { | |
| "cell_type": "markdown", | |
| "metadata": {}, | |
| "source": [ | |
| "# The unreasonable effectiveness of Character-level Language Models\n", | |
| "## (and why RNNs are still cool)\n", | |
| "\n", | |
| "###[Yoav Goldberg](http://www.cs.biu.ac.il/~yogo)\n", |
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.
| (require :drakma) | |
| (require :cl-ppcre) | |
| (defvar *weather-url* "http://forecast.weather.gov/MapClick.php?zoneid=NYZ075&TextType=1" | |
| "The url we'll be going to, to get the weather information") | |
| (defun starts-with (regexp string) | |
| "Checks to see if a string starts | |
| with the given regexp" | |
| (eq (search regexp string) 0)) |
| import java.io.FileDescriptor; | |
| import java.io.FileOutputStream; | |
| import java.io.IOException; | |
| import java.io.OutputStream; | |
| import java.io.PrintStream; | |
| public class HelloWorld{ | |
| private static HelloWorld instance; | |
| public static void main(String[] args){ | |
| instantiateHelloWorldMainClassAndRun(); |
Follow Go community standards:
