When is a code base a single file?

Multiple people can use the same code base

Code base examples

React Repository on Github

Where does a code base live?

Why are code bases important?

Code bases make it easier to scale a project

Establishing rules

Linting rules

Conclusion

Step 1 - High Level Understandings

Step 2 - Exploring the code base

Step 3 - Cloning and getting the repo locally

Step 4 - Exploring some frontend code (Buttons.stories)

Step 5 - Main Application

Email Testing

Learnings from the video

Bye Bye!

Intro

Folder Structure

Extensions and Setting Up the Environment

Learn Version Control

What we'll cover in this video

In the real world, documentation isn’t always available

Exploring 3 different web apps to gain insight on what they do

Taking a look at a closed source Flask application

Figuring out the tech stack of the application from the bottom up

Scoping out a project’s size on the command line in a few seconds

Determining how an app is designed based on lines of code for file types

Using prior experience and our new found knowledge to find out what to edit

Looking at an open source Phoenix app ( on GitHub

One strategy for fixing a bug in an open source project

First steps to get familiar with an open source project’s code base

Using GitHub’s UI to gain insights on an application’s code base

Repeating most of what we did on the command line but on GitHub instead

Copying features from an open source project into your project

Tracing code on a need to know basis

Not every pull request needs to be Earth shattering, small is ok

You don’t need to be an expert or professional to contribute to a project

Don’t under estimate small pull requests, always test your code!

Looking at a Ruby on Rails open source project ( on GitHub

Seeing what the dev.to code base is composed of

Exploring the routes at the code level (some web frameworks have this)

Repeating what we did previously to find the dev.to tech stack

Finding hints of a linting tool being used is a very good sign for code quality

Tests are a great way to see how things work under the hood

Use everything together and your task at hand to determine what to do next

Introduction

Code Walkthrough

Intro

How to integrate into a new codebase?

Read the documentation

What to do if there is no documentation

Self-discovery tips

Stepping through code

Step through the code using breakpoints and other tools to help you understand the flow of the code

Write unit tests to practice your understanding of the code

Document everything you learn

Conclusion

Intro

Docs

Key areas

Tooling

Depth

Formation

Expand

Video Intro

Link to another of my videos on understanding code written by others

Take on small tasks to get hands-on in a new codebase

Get some mentors to help you become familiar with a codebase

Ask someone to give a walkthrough of new code functionality

Reading documentation and wiki to help learn a new codebase

Use code reviews to learn a new codebase quickly

Institute a "no progress" rule to prevent prolonged stagnation

Linux kernel 0.0.1 First release of Linux

Photoshop 1.0 1990 First release of Photoshop

Version 7 UNIX Final Research

Camino macos web browser

BASH Preeminent Unix shell

GIMP Open-source graphics editor

4.4 BSD-Lite Release 2 1995 Final release of BSD operating system

Debian 7.0

Who is Cody?

Trying it on the Laravel framework

How do I add a scope?

Trying it on an obscure repo

Using Cody to fix our code

Code generation

Cody is GA, with a few rough edges

The Foundry

Codebase

How Does Codebase Benefit

Genetic Approaches

Package Code Base

Sdks

The Difference between Patents and Trade Secrets

Compounding Opportunity of the Code Base