New Cohort Starts:

Donate
← Back to the skill map
Systems & Tooling/Systems & practice

Streams & Pipes

4 micro-topics in Systems & Tooling, each with the evidence that proves you have it and the written reason behind every link. Before you start, it rests on 2 other domains. Downstream, it holds up 1 domain.

4 topics  ·  depth 3–5 of 16  ·  3 internal links  ·  2 in  ·  1 out

Before you start

Load-bearing links first. Each one says what in this domain rests on what outside it, and why.

Filesystem

1 link

load-bearing

Reason about stdin, stdout and stderr rests on Inspect file contents

Streams are the abstraction behind reading and writing files.

Text Processing

1 link

supporting

Compose commands with pipes rests on Search text with grep

Pipelines are only worth building once you have tools to chain.

What you will be able to do

In prerequisite order. Each idea names the artifact that closes it, the market demand that put it on the map, and what it stands on.

Depth 3  ·  conceptual  ·  unassisted  ·  M01 §1.4

Reason about stdin, stdout and stderr

Knows which stream output is going to

Evidence
Separates errors from results in a single command
Market anchor
Linux
Rests on
load-bearing

Inspect file contents · Filesystem

Streams are the abstraction behind reading and writing files.

Depth 4  ·  procedural  ·  unassisted  ·  M01 §1.4

Redirect output to files

Applies >, >>, 2> and 2>&1 correctly

Evidence
Captures errors and output to separate files
Market anchor
Command line
Rests on
load-bearing

Reason about stdin, stdout and stderr

Redirection sends a stream somewhere, so the stream comes first.

Depth 4  ·  procedural  ·  unassisted  ·  M01 §1.4

Compose commands with pipes

Chains tools so one's output feeds the next

Evidence
Answers a question about a log with a three-stage pipeline
Market anchor
Command line · data processing
Rests on
load-bearing

Reason about stdin, stdout and stderr

A pipe connects one command's stdout to another's stdin.

supporting

Search text with grep · Text Processing

Pipelines are only worth building once you have tools to chain.

Depth 5  ·  procedural  ·  scaffolded  ·  M01 §1.4

Substitute command output

Uses $(command) and xargs to pass values along

Evidence
Feeds one command's results into another as arguments
Market anchor
Shell scripting
Rests on
load-bearing

Compose commands with pipes

Substitution is the next step after chaining output.

What rests on this domain

Everything downstream that names an idea here as a prerequisite, grouped by where it lives.

Shell Scripting

1 link

load-bearing

Write and run a shell script rests on Compose commands with pipes

A script is a saved pipeline plus control flow.

Retool. Retrain. Relaunch.

375 ideas. 17 weeks. No tuition, ever.

Vets Who Code is a veteran-run 501(c)(3). The accelerator is free, remote, and we don’t take a share of your first paycheck.

Free · Remote · 17 weeks · EIN 86-2122804