Skip to content
BENIBIX Learn

Learn Code Editors and Package Managers

The tools you work in every day once you start to code. Thirteen lessons start with the editor, what it adds to plain text, and the keyboard editors that run in a terminal. Then come the tools that check your code, and the debugger that stops it mid-run. The rest is about other people's code: how a package manager fetches it, pins it and builds it. It assumes nothing. It stops at the tools. The languages themselves are a separate subject.

Not started

0 of 13 lessons done

13 lessons5 sections~3 h47 termsSee the wordsBasic

Level 1 · The editor

score0250/10 words

Where you write code, and what an editor adds to plain text. The big apps, the add-ons, and the editors you drive with keys.

  1. Code Editors and IDEsWhat a code editor is, and how an IDE differs. Why VS Code is the most used editor, and when a JetBrains IDE is worth its size.11 min4 terms
  2. Autocomplete and ExtensionsWhat the colours in your code mean. How the editor guesses your next word, and how an add-on gives your editor a new skill.10 min3 terms
  3. Vim, Neovim and EmacsThe editors you drive with keys, inside a terminal. How Vim's modes work, what Neovim changed, how Emacs grows, and how to quit each one.11 min3 terms

Level 2 · Checking and fixing code

score25450/8 words

The tools that read your code before it runs, and the ones that help you find a bug once it does.

  1. Linters and FormattersHow a linter warns about likely bugs, and how a formatter tidies the layout. Why ESLint and Prettier are two tools, and how to run both.12 min4 terms
  2. Debuggers and BreakpointsHow a debugger pauses your program on a breakpoint so you can look inside. When a print line or a rubber duck finds the bug faster.12 min4 terms

Level 3 · Trying code out

score45550/3 words

The places to run one line and see the answer at once. A prompt, a notebook, and the tools in your browser.

  1. REPL, Notebooks and DevToolsThree places to try code and see the answer at once. A REPL runs in the terminal. A notebook saves it. DevTools sit in the browser.11 min3 terms

Level 4 · Other people's code

score55850/19 words

Libraries, frameworks and the packages they come in. The tools that fetch them, and how to keep their versions from breaking your work.

  1. Libraries, Frameworks and SDKsCode you reuse so you do not have to write it. How a library and a framework differ, what an SDK holds, and what each one costs you.11 min4 terms
  2. Package Managers, npm and pipWhat a package is, where it lives, and how a package manager fetches it. How npm does it for JavaScript and pip for Python.12 min5 terms
  3. Yarn, pnpm, Cargo and HomebrewThe other package managers you will meet. Yarn and pnpm in place of npm, Cargo for Rust, and Homebrew for apps on a Mac or Linux.11 min4 terms
  4. Lockfiles and Version PinningHow a lockfile makes every install the same, what the ^ in a version means, and how pinning helps. What dependency hell is, and how to stay out of it.13 min3 terms
  5. Virtual Environments and uvEach Python project gets its own packages in a virtual environment. A version manager swaps the language. And uv does both in one tool.12 min3 terms

Level 5 · Building the project

score851000/7 words

The tools that turn code into a program. They run the team's jobs by name, and write a new project's first files.

  1. Make, Maven and GradleWhat a build tool does, and how it skips work that has not changed. Make with its Makefile, Maven with pom.xml, and Gradle for Java and Android.13 min4 terms
  2. Task Runners and ScaffoldingHow npm scripts give each job a short name. How one command can write all the first files of a new project for you.11 min3 terms

Words in this course

The 47 glossary entries this course teaches, in the order it teaches them. Open any of them on its own.

Back to the top

See what comes after this course