Versions Compared

Old Version 22

changes.mady.by.user Anthony Bernardi

Saved on

compared with

New Version 23

changes.mady.by.user Reid Chandler

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Git: What is it and why?

    1. Git is a version control system and GitHub is an internet hosting service using the version control that Git provides. If you are not familiar with Git, you can find a great presentation on what Git is here. Some other resources include common git commands, CLI commands, and what Git is (if you get the gist you do not need to read through all of it).

    2. In order to set up Git on your computer please follow these steps (after creating a GitHub account if you do not already have one). Make sure to do the authentication step so that your computer is tied to your GitHub account.

    3. Now that you have Git installed and have a GitHub account, clone the repository from here to your computer, potentially using git clone in your preferred CLI (i.e. Terminal/Powershell; please use Powershell over Command Prompt on Windows) to pull the project down to your computer. 

  2. NodeJS: Version 14 16 18 Please

    1. Ensure that you have Node.js v16 installed (14 also works though, 18 doesn’t)v18 installed. Any iteration of version 16 18 will do as long as it is version 1618! https://nodejs.org/en/blog/release/v16.16.0/

    2. Check the box to install any additional tools during installation to ensure functionality with VSCode while installing (don’t worry if there are a couple errors here - this tends to happen on new installs).

    3. After installation, confirm that the version is some variant of 16 with the command node -v.

  3. NPM & Yarn

    1. Navigate to the folder of the cloned repository using your CLI (via the cd command).

    2. If you’re on Windows: run Set-ExecutionPolicy -ExecutionPolicy RemoteSigned to prevent some future problems with yarn

    3. In your CLI, run npm install -g yarn.

    4. Run yarn install to instruct npm to install all the necessary packages.

...

Our Product Team exists as a wonderful resource for all developers on the Software Solutions team. Product Analysts, Product Managers, and our Head hold key business facing information for all parts of our application, and are a great resource to go to if you have non-technical questions. Make sure to reach out to relevant analysts, PMs, or even Leroy Peyton first before reaching out to others for these questions in case they can answer your questions.

For technical or coding questions, try to contact anyone you are pair programming with or working with on a feature. If this does not help, move to the tech leads & senior developers. Next step is to check in with a Software Group Lead, Reid Chandler or Arnav JoshiPeyton McKee. If they cannot answer anything, please contact the Head of Software Solutions, Anthony Bernardi. After that only the president, James Chang-Davidson, can help you 😳 (he doesn’t bite)Reid Chandler.