Browse Source

make things more readable on github

pull/1/head
Brennen Bearnes 7 years ago
parent
commit
b1a1afa70a
6 changed files with 26 additions and 17 deletions
  1. +16
    -11
      README.md
  2. +1
    -0
      further_reading/README.md
  3. +1
    -0
      literary_environment/README.md
  4. +1
    -0
      literary_problem/README.md
  5. +1
    -0
      programmerthink/README.md
  6. +6
    -6
      programmerthink/index.md

+ 16
- 11
README.md View File

@ -1,14 +1,21 @@
userland: a book about the command line for humans
==================================================
A [recent side trip](//p1k3.com/2013/8/4) into simple text utilities got me
thinking about how many of my writing habits depend on the Linux command line.
This struck me as a decent hook for talking about the tools I use with an
audience of mixed technical background (a handful of old Unix heads from way
back, some engineers and hard science types, some gamers & Windows people, some
poets and musicians).
This is a work in progress.
WORK IN PROGRESS.
Late last year, [a side trip](//p1k3.com/2013/8/4) into simple text utilities
got me thinking about how many of my writing habits depend on the Linux command
line. This struck me as a decent hook for talking about the tools I use every
day with an audience of mixed technical background.
So now I'm writing a (short, haphazard) book. This isn't a book about system
administration, or writing big software systems, or becoming a wizard. I am
not a wizard, and I don't subscribe to the thesis that wizardry is a
requirement for using these tools. I barely know what I'm doing most of the
time, but hey, I get some stuff done.
(If you're a friend of mine and I've asked you to take a look at this, don't
feel bad if you don't get around to it. It's all dry as day-old toast.)
-- bpb
@ -19,19 +26,17 @@ contents
2. [a literary problem](literary_problem/)
3. [programmerthink](programmerthink/)
4. [diff](diff/)
4. [further reading](further_reading/)
5. [further reading](further_reading/)
TODO
----
- some sidebars
- what the hell is a filesystem, anyway?
- some sidebars
- fmt
- ptx?
- sed
- nl
- find
- ack?
- Markdown, LaTeX, etc.
- fix up the licensing section


+ 1
- 0
further_reading/README.md View File

@ -0,0 +1 @@
index.md

+ 1
- 0
literary_environment/README.md View File

@ -0,0 +1 @@
index.md

+ 1
- 0
literary_problem/README.md View File

@ -0,0 +1 @@
index.md

+ 1
- 0
programmerthink/README.md View File

@ -0,0 +1 @@
index.md

+ 6
- 6
programmerthink/index.md View File

@ -253,12 +253,12 @@ of lines of text to extract a specific string. If a directory has a
`index`.
What are the downsides? Well, it requires transforming lots of text files into
directories-containing-files. It would be easy to automate that process, but
it's a little tedious and it makes the layout of the entry archive more
complicated overall. There's a cost to doing things this way. It lets me
extend my existing model of a blog entry to include arbitrary metadata, but it
also adds steps to writing or finding blog entries.
directories-containing-files. I might automate that process, but it's still a
little tedious and it makes the layout of the entry archive more complicated
overall. There's a cost to doing things this way. It lets me extend my
existing model of a blog entry to include arbitrary metadata, but it also adds
steps to writing or finding blog entries.
It turns out that most abstractions cost you something. Is this one worth it?
Abstractions usually cost you something. Is this one worth the hassle?

Loading…
Cancel
Save