Skip to content

Instantly share code, notes, and snippets.

In <http://boston.conman.org/2009/11/05.1>, “The dinosaur that I am”,
Sean Conner (spc476) suggests a sort of silly bare-metal problem...
> to most programmers, even a simple text editor is a crutch.
>
> Imagine being given a 1982 era IBM PC with a floppy drive and a
> single disk that contains a bootable MS-DOS system with IO.SYS,
> MSDOS.SYS and COMMAND.COM (the minimum required to boot to a usable
> (for various values of “usable”) system at the time) and a stack of

After many years of writing and thinking about developer documentation, I'm convinced that the discipline is still in its infancy. The goal of this document is to summarize my current opinions on the topic of documenting software.

When you ask a software developer what their favorite documentation is, you'll get a wide range of opinions with consensus centering roughly around the Stripe and Twilio documentation, as well as the documentation for open source software like Django, Perl, Flask, etc.

In academia, the uncontested master craftsman of developer documentation is Donald Knuth, who pioneered "Literate Programming"

At the frontier of developer documentation, we find projects like Eve and other projects inspired by Bret Victor's seminal "Inventing on Principle" video.

However, as Bret Victor will often point out, the medium (in the McLuhan sense of the word) of software hasn't changed much since the days when code was written on teletypes: We still write software on fancy typewriters. The tragedy o

#!/bin/bash
# get_id_token.sh
# A shell script which demonstrates how to get an OpenID Connect id_token from from Okta using the OAuth 2.0 "Implicit Flow"
# Author: Joel Franusic <joel.franusic@okta.com>
#
# Copyright 2016, Okta Inc
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at