Installing stuff without fear | Master AI Automation in 4 hours Master AI Automation in 4 hours Course About Ayush Modules Sample chapter Toolbox The Microcap Minute Classroom / Module 03: The Command Line / Chapter 5 Installing stuff without fear Watch first, then read. Same lesson, your pace. What you will learn – Why package managers beat downloading installers – The three you’ll actually use: Homebrew, pip/uv, npm – Virtual environments: Python’s mess-containment system The app store for everything Downloading installers from websites is the old way, slow, unsafe, un-updatable. The terminal way is a package manager : one tool that installs anything from a trusted catalogue, tracks versions, and updates all of it with one command. Homebrew (Mac/Linux), the general installer: brew install wget # any CLI tool brew install –cask firefox # even regular apps pip / uv (Python), this course’s main character, since most AI scripting is Python: pip install requests # the classic uv pip install requests # uv = pip’s 100x-faster modern replacement npm (JavaScript), matters later when MCP servers arrive: npm install -g typescript # -g means globally available When a tutorial says “install X”, it will almost always mean one of these three patterns. You now recognise all of them. PATH: why “command not found” happens When you type python , the computer searches a list of folders (called PATH ) to find a program with that name. Install something and it’s not found? Ninety percent of the time the fix is boring: close the terminal and open a new one. Installers update your PATH only for new sessions. Second-most-common cause: the tool installed under a slightly different name ( python3 vs python ). Try both before panicking. Virtual environments: contain the mess Python projects need libraries; different projects need different versions of the same library. Installing everything globally eventually breaks something. The fix is a virtual environment (venv) : a private bubble per project. cd ai-workspace/projects/my-first-project python3 -m venv .venv # build the bubble source .venv/bin/activate # enter it (Windows: .venvScriptsactivate) Your prompt gains (.venv) , you’re inside. Now pip install affects only this project. Leave with deactivate . Rule of thumb: one venv per project, always. This five-line ritual prevents the classic “why does my Python hate me” spiral entirely. Try it yourself Check what you already have: python3 –version , node –version ( npm –version ), and on Mac brew –version . Missing ones are fine, note them. Then create your first venv in projects/test-env/ , activate it, run pip install requests , and prove existence: python3 -c “import requests; print(requests.__version__)” . Deactivate. Congratulations, you’ve done the exact setup real AI projects use, and Module 4 will reuse this bubble. Key takeaways – Package managers (brew/pip-uv/npm) are the safe, fast way to install software. – “Command not found” usually means new-terminal or name-variant, not disaster. – One virtual environment per project keeps dependencies from colliding. – Activate → install → deactivate: the ritual that keeps Python sane. Download the exercise sheet (PDF) Module workbook (PDF) ← Prev: Looking inside Next: IDEs vs the command line → Classroom / Module 03: The Command Line / Chapter 5 Installing stuff without fear What you will learn – Why package managers beat downloading installers – The three you’ll actually use: Homebrew, pip/uv, npm – Virtual environments: Python’s mess-containment system The app store for everything Downloading installers from websites is the old way, slow, unsafe, un-updatable. The terminal way is a package manager : one tool that installs anything from a trusted catalogue, tracks versions, and updates all of it with one command. Homebrew (Mac/Linux), the general installer: brew install wget # any CLI tool brew install –cask firefox # even regular apps pip / uv (Python), this course’s main character, since mo
Installing stuff without fear
Written by
in