Skip to content

Instantly share code, notes, and snippets.

View hjr3's full-sized avatar

Herman J. Radtke III hjr3

175 followers · 15 following
View GitHub Profile
@hjr3
hjr3 / dc_2017_biblio.md
Last active November 16, 2017 11:38 — forked from BaseCase/dc_2017_biblio.md
List of resources recommended or mentioned by the speakers at Deconstruct 2017

Deconstruct 2017 Bibliography

Here are all of the resources mentioned by Deconstruct 2017 speakers, along with who recommended what. Please post a comment if I missed something or have an error!

DC 2017 Speakers' Choice Gold Medalist

  • Seeing Like a State by James Scott

Books

  • Public Opinion by Walter Lippmann (Evan Czaplicki)
  • A Pattern Language by Christopher Alexander (Brian Marick)
  • Domain Driven Design by Eric Evans (Brian Marick)
@hjr3
hjr3 / fork-exec.rs
Created December 23, 2016 02:01 — forked from Geal/fork-exec.rs
extern crate nix;
extern crate libc;
use nix::sys::signal::*;
use nix::unistd::*;
use nix::fcntl::{fcntl,FcntlArg,FdFlag,FD_CLOEXEC};
use libc::c_char;
use std::mem;
use std::str;
@hjr3
hjr3 / adams-heroku-values.md
Created December 4, 2015 03:39 — forked from adamwiggins/adams-heroku-values.md
My Heroku values

Make it real

Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.

Ship it

Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

Do it with style

@hjr3
hjr3 / gist:cf351d03f0090683eb5f
Created July 23, 2014 00:27

I'm sick right now and probably have a fever, so this may make little sense or be completely incorrect. For years, I've been tossing this strange idea around in my head. The goals are:

  • Make associative and sparse data structures cheap and fast.
  • Make memory management trivially simple (no two-step process of adjusting data segment, then allocating from within it; no per-process address spaces).
  • Make memory allocation time very consistent, if not constant.

Note that I have at best a basic understanding of most of the topics here and this is probably pathologically naive. This is not a blog post; it's the kind of thing that I'd send to a friend who knows more than me about these topics.