jsmankoo/code

How we operate (so well).

Legend

1. Introduction

• Routines
  • Standup
  • [Sprint Plan](Sprint Plan)
  • [Cleanup Hour](Cleanup Hour)
  • [Bug Smash Sesh](Bug Smash Sesh)
  • [Lunch n' Learn](Lunch n' Learn)
• Processes
  • Architecture
  • [Pivotal Tracker](Pivotal Tracker)
  • [Pull Requests](Pull Requests)
  • [Code Reviews](Code Reviews)
  • Release
• Coding Practices
  • [Naming Conventions](Naming Conventions)
  • [Style Guides](Style Guides)
  • Branches
  • Commits
  • Testing
• Other
  • Karma
  • Tools

Introduction

Purpose

At PumpUp, we hold high standards for the quality of code that powers any of our products. Maintaining a healthy codebase is crucial for large-scale applications to be able to move fast and iterate often.

So, we are creating this guide – an ever-evolving story of how we operate, from avoiding semicolons to shooting Nerf™ guns.

Organization

Each listing in the directory above is a chapter on different aspects of writing code.

Within each chapter is a README.md file that talks about a concept with some generic examples.

Along with each chapter’s README.md file, there may also be a language specific file, such as JavaScript.md, Swift.md, and Java.md, that goes in depth of how that concept relates to the language.

Improvements

At any point in your development, if you learn something new, please document it! This is a continuous work in progress and is only as good as we make it.

If you're unsure as to whether or not your changes are appropriate, open a [PR](Pull Requests).

Thanks for reading!

Made with ❤️ by your fellow teammates at PumpUp.