proomt

Search

Search posts, papers, and topics

All posts

Hacker News front pageWill Keleher7 min readintermediate

Telling a Computer to Do Things

Summary

The author explains how learning shell scripting unlocked the ability to automate and stitch together tools, emphasizing that proficiency is more about a rich CLI toolbox than syntax. He provides concrete tips, tool suggestions, and examples for writing maintainable scripts.

  • Shell scripts let you combine commands with control flow (if, loops, pipes) to automate complex tasks.
  • Mastering the shell is 20% syntax, 80% knowing useful CLI tools like fzf, xargs, rsync, direnv, duckdb, gh.
  • For teams comfortable with JavaScript, the zx library offers a more ergonomic way to write shell‑style scripts.
  • Simplify error handling: use `if ! cmd; then …` instead of toggling `set +e` and checking `$?`.

Engineers who write build, deployment, or test automation should know shell scripting to create reliable, maintainable workflows.

5/10

Related reading

  1. Blog: How to Build a DevOps Agent

    This blog walks through the open‑source DevOps Agent Kit, which lets Claude Code or Cursor act as a DevOps assistant by connecting to CloudBees Unify, Jira, and Slack via MCP servers and to GitHub via the CLI. It provides a repeatable setup (Docker, Node, env file) and seven slash commands for pipeline overview, triage, security, release readiness, flag management, CI health scoring, and Jira tic…

    Codeshipcloudbees.com10 min
  2. Presentation: Complexity and Creativity in Software Engineering

    Phillip Mortimer argues that AI‑generated code makes all software effectively "write‑only" due to volume, and proposes managing this by treating tests as the sole specification, automating code reviews with LLMs, and decoupling intent from implementation.

    InfoQinfoq.com28 mintalk