New Cohort Starts:

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

Shell Configuration

5 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 1 other domain. Downstream, it holds up 5 domains.

5 topics  ·  depth 0–5 of 16  ·  4 internal links  ·  1 in  ·  5 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

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 0  ·  procedural  ·  guided  ·  M01 §1.5

Customize the shell prompt

Encodes useful state into PROMPT

Evidence
Shows branch and directory in the prompt
Market anchor
Shell
Rests on
supporting

Write aliases and shell functions

Prompt customization is the same file and the same syntax.

Depth 3  ·  conceptual  ·  scaffolded  ·  M01 §1.5

Explain shell startup files

Distinguishes .zshrc, .zprofile and .zshenv

Evidence
Puts a setting in the file that actually loads it
Market anchor
Linux · shell
Rests on
load-bearing

Work with hidden files and dotfiles · Filesystem

Startup files are dotfiles.

Depth 4  ·  procedural  ·  unassisted  ·  M01 §1.5

Manage environment variables

Exports and inspects variables with export and printenv

Evidence
Sets a variable a child process can read
Market anchor
Linux · configuration
Rests on
load-bearing

Explain shell startup files

Variables are set in the files that load at startup.

Depth 4  ·  procedural  ·  unassisted  ·  M01 §1.5

Write aliases and shell functions

Shortens repeated commands into named ones

Evidence
Ships a .zshrc with working aliases for daily work
Market anchor
Shell scripting
Rests on
load-bearing

Explain shell startup files

Aliases live in the startup file.

Depth 5  ·  conceptual  ·  unassisted  ·  M01 §1.5

Configure PATH

Adds directories and understands why order matters

Evidence
Resolves a wrong-binary problem by reordering PATH
Market anchor
Linux
Rests on
load-bearing

Manage environment variables

PATH is an environment variable with rules.

What rests on this domain

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

Delivery & CI/CD

1 link

load-bearing

Manage secrets and environment config rests on Manage environment variables

Configuration reaches the process as environment.

Package Managers

1 link

load-bearing

Install system packages rests on Configure PATH

Installed binaries are only usable if PATH resolves them.

Shell Scripting

1 link

load-bearing

Write and run a shell script rests on Configure PATH

Running a script by name requires PATH resolution.

Validation & Pydantic

1 link

load-bearing

Manage configuration as typed settings rests on Manage environment variables

Configuration comes from environment variables.

Version Control

1 link

supporting

Configure Git and ignore rules rests on Write aliases and shell functions

Git aliases are the same idea as shell aliases.

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