Available now

The command line, for data.

The terminal looks old-fashioned, which is exactly why it is everywhere. Servers have no mouse. Log files are too big to open. A pipeline that broke at 2am gets fixed by typing.

You learn the handful of commands data engineers actually use, on real CSV files and logs, and how to snap them together with pipes.

Why data engineers need it

  • Servers, containers and cloud machines are driven from a terminal.
  • Checking a file before you load it takes seconds with head and wc.
  • Logs are text: grep finds the one error in a million lines.

What you will learn

  • Moving around folders with pwd, ls and cd
  • Peeking at files of any size with head and tail
  • Counting rows and filtering lines with wc and grep
  • Pipes: chaining small tools into one command
  • A GROUP BY for files with cut, sort and uniq
  • Saving results with > and >>

The lessons

  1. 1The command line for dataFreeLook inside huge files without opening them, count, filter and group from the terminal, and pull errors out of a log.

Questions

Which terminal is this, Mac or Windows?
It behaves like the terminal on Mac and Linux servers, which is what data engineers use day to day. The same commands work in Windows through WSL or Git Bash.
Can I break anything?
No. Everything happens in a practice folder inside your browser.

Nothing to install. Nothing to break.

Every lesson runs in your browser, on your laptop or your phone.

Try it now