diff --git a/tech_docs/javascript.md b/tech_docs/javascript.md
new file mode 100644
index 0000000..1bb3fce
--- /dev/null
+++ b/tech_docs/javascript.md
@@ -0,0 +1,100 @@
+Sure, here's a complete reference guide for a programmer coming from the Python world and getting into JavaScript programming, specifically focusing on package management and project setup:
+
+# From Python to JavaScript: A Guide for Package Management and Project Setup
+
+If you're a Python developer transitioning to JavaScript programming, you'll encounter some similarities as well as differences in how packages and dependencies are managed. This guide aims to provide you with a comprehensive overview of package management and project setup in the JavaScript ecosystem, drawing parallels with Python's tools and concepts you're familiar with.
+
+## Understanding Node.js and npm
+
+In the JavaScript world, Node.js is a runtime environment that allows you to run JavaScript code outside of a web browser. Node.js comes bundled with `npm` (Node Package Manager), which is the default package manager for installing and managing packages and dependencies.
+
+`npm` is similar to Python's `pip` in that it is used to install packages from a central repository (in this case, the npm registry at https://www.npmjs.com/). However, unlike `pip`, `npm` is also responsible for managing project-level dependencies and generating a `package.json` file, which serves a similar purpose to Python's `requirements.txt`.
+
+## The `package.json` File
+
+The `package.json` file is the heart of a Node.js project. It contains metadata about the project, such as its name, version, description, and author, as well as a list of dependencies and scripts for various tasks.
+
+The dependencies are divided into two categories:
+
+- `dependencies`: Packages required for the production environment.
+- `devDependencies`: Packages required only for development purposes, such as testing frameworks, linters, or build tools.
+
+This separation is similar to how you might separate your production requirements from your development requirements in Python projects.
+
+## Node Modules and Virtual Environments
+
+In Node.js, there is no built-in concept of virtual environments like Python's `venv` or `conda`. Instead, all the installed packages and their dependencies are stored in a `node_modules` directory within your project.
+
+This `node_modules` directory serves a similar purpose to Python's virtual environment, isolating the project's dependencies from other projects on the same machine. However, unlike Python's virtual environments, which create separate instances of the Python interpreter, the `node_modules` directory only isolates the packages and dependencies, not the Node.js runtime itself.
+
+## Using npm or yarn
+
+While `npm` is the default package manager that comes bundled with Node.js, many developers prefer using an alternative called `yarn`. `yarn` was introduced by Facebook in 2016 and offers faster installation times, better dependency management, and reproducible builds.
+
+The choice between `npm` and `yarn` is analogous to the choice between `virtualenv` and `venv` (or `conda`) in Python. While `npm` is the legacy option, `yarn` is considered the more modern and preferred choice by many developers, similar to how `venv` is preferred over `virtualenv` in Python.
+
+## Setting Up a New Project
+
+Here's a step-by-step guide to setting up a new JavaScript project using `yarn`:
+
+1. **Install Node.js**: First, you'll need to install Node.js on your machine. You can download the latest version from the official website: https://nodejs.org/en/download/
+
+2. **Install yarn**: Open your terminal or command prompt and run the following command to install `yarn` globally:
+
+   ```
+   npm install --global yarn
+   ```
+
+3. **Initialize a new project**: Navigate to the directory where you want to create your new project and run the following command to initialize a new `package.json` file:
+
+   ```
+   yarn init
+   ```
+
+   This will prompt you to provide metadata about your project, such as the project name, version, description, and more.
+
+4. **Install packages**: To install a package, run the following command:
+
+   ```
+   yarn add package-name
+   ```
+
+   This will add the package to the `dependencies` in your `package.json` file and download the package and its dependencies into the `node_modules` directory.
+
+5. **Install development dependencies**: To install a package as a development dependency, run the following command:
+
+   ```
+   yarn add --dev package-name
+   ```
+
+   This will add the package to the `devDependencies` in your `package.json` file.
+
+6. **Start your project**: Many JavaScript projects, especially those using frameworks like React or Gatsby, provide scripts for starting a development server or building the project. You can run these scripts using the following command:
+
+   ```
+   yarn run script-name
+   ```
+
+   For example, to start a Gatsby development server, you might run `yarn run develop`.
+
+## Managing Dependencies
+
+Once your project is set up, you can use `yarn` (or `npm`) to manage your project's dependencies:
+
+- **Updating packages**: To update a package to its latest version, run `yarn upgrade package-name`.
+- **Removing packages**: To remove a package, run `yarn remove package-name`.
+- **Installing from `package.json`**: If you're working on an existing project or sharing a project with others, you can run `yarn install` (or `npm install`) to install all the required dependencies listed in the `package.json` file.
+
+## Lockfiles and Reproducible Builds
+
+Both `yarn` and `npm` generate lockfiles (`yarn.lock` and `package-lock.json`, respectively) to ensure that everyone installing the project's dependencies gets the exact same package versions. This ensures consistency across different environments and reproducible builds.
+
+These lockfiles are automatically generated and should be committed to your version control system, along with the `package.json` file.
+
+## Conclusion
+
+While there are some differences between the Python and JavaScript ecosystems when it comes to package management and project setup, the overall concepts are similar. By understanding the role of `npm` or `yarn`, the `package.json` file, and the `node_modules` directory, you'll be well-equipped to manage dependencies and set up new projects in the JavaScript world, just like you would in Python.
+
+Remember, both `npm` and `yarn` are widely used and supported in the JavaScript ecosystem, but `yarn` is generally considered the more modern and preferred choice, similar to how `venv` is preferred over `virtualenv` in Python.
+
+With this guide, you should have a solid understanding of how to transition from Python's package management tools to the JavaScript ecosystem, making it easier for you to work on and contribute to JavaScript projects, including those using popular frameworks like React or Gatsby.
\ No newline at end of file