IntrepidPursuits / sherpa

Development best practices for Intrepid

Sherpa

Development best practices for Intrepid

Contribution rules:

• Two developers must approve before merging contributions
• One developer veto blocks contribution for review & revision
• Use the github issue functionality if you find something is missing & should be added to Sherpa

Platform-specific Resources

• iOS
  • Estimation Playbook
  • Project Setup
  • Stuff to read for iOS devs
  • CocoaPods Processes
  • CocoaPods Best Practices
  • Common CocoaPods
  • iOS Recommended Tools
  • Inspecting an .ipa file
  • Firebase Gotchas
  • Rx Best Practices
  • Rx Swift by Example
  • Testing References
  • iOS App Submission Checklist
• Android
  • New project setup instructions
  • Stuff to read for Android devs
  • Useful Android Studio plugins
  • Tidbits
• Web
  • Intro to service objects
  • Deploying Phoenix/Elixir apps
  • Testing ReactJS apps
  • React and Recompose
  • Deploying ReactJS apps
  • Best Practices on Caching
  • Setting up a Rails app
  • CSS style guide
  • Rails gem gotchas
  • Javascript gotchas
  • Rails gotchas
  • MEAN stack glossary

Jenkins

• Configuration for all platforms
  • Intrepid Jenkins Configuration

Style Guides

• iOS
  • Swift
  • Objective-C
• Android
  • Android OS Project Style Guide
  • Intrepid Style Template
• Ruby
• Elixir
• C#

Process

• Intrepid Development Principles

Git

• Git Workflow
• Pull Request Guidelines
• Why rebase?
• Writing a good commit message
• Git cookbook

Maintenance Readme Template

Projects repos should always contain a README so that future development teams can learn about processes/specific quirks that have to do with individual projects. See the template here.

Advice

• Mobile API Guidance

General Resources

• Intrepid internal resources
• Comparison of Android and iOS development