The Best Tech Team in the World Ever, Ever, Ever!

Get Started. It's Free
or sign up with your email address
Rocket clouds
The Best Tech Team in the World Ever, Ever, Ever! by Mind Map: The Best Tech Team in the World Ever, Ever, Ever!

1. Testing

1.1. Unit Testing

1.1.1. Individual tests run under a second

1.2. Integration Tests

1.2.1. Not bound to the data

1.2.2. Pass or Fail Consistently

1.3. Code Coverage

1.3.1. >=90%

1.3.2. Transparent to the team

1.4. Performance Testing

1.5. A/B Testing

1.6. User Acceptance Testing

1.6.1. Frequent involvement of end users

1.6.2. User Feedback

1.6.2.1. User Insights Tool

1.6.3. Environment

1.6.3.1. TraineeUI

1.6.3.2. Already have one?

1.7. Error Reporting

1.7.1. Error Tracking Tool

1.7.1.1. Sentry?

1.8. Quality Testing

1.8.1. Linting

1.8.2. Styling

1.8.2.1. Style Guide

1.8.3. Reportable

2. Code

2.1. Best Practices

2.1.1. Style Guide

2.1.1.1. Google

2.1.1.1.1. FE

2.1.1.1.2. BE

2.1.2. DRY Principle

2.1.3. Boy Scout

2.1.3.1. Refactoring

2.1.4. Commenting Code

2.1.4.1. Top level Comments

2.1.4.2. Function Comments

2.1.4.3. Helpful Comments

2.1.4.3.1. e.g. Edge Cases

2.1.4.4. No Jokes

2.1.4.5. No References to other companies

2.1.5. KISS - Kiss It Simple Stupid

2.1.5.1. Simplest Solution

2.1.6. Code Reviews

2.1.6.1. Small Pull Requests

2.1.6.2. Small Commits

2.1.6.3. Code Sharings

2.1.6.4. Early Visibility

2.1.6.4.1. Draft PRs

2.1.6.5. Comments on PRs

2.1.6.6. Replies on PRs

2.1.6.7. RESPECT!

2.1.6.7.1. Block on PRs

2.1.6.7.2. Comments on PRs

2.1.6.8. Transparent

2.1.6.8.1. Accessible

2.1.6.9. Check approved PRs

2.1.6.10. Commit Messages

2.1.7. Commit Messages & PRs

2.1.7.1. Make Sense!

2.1.7.2. No Jokes

2.1.7.2.1. no "fixy fixy"

2.1.7.3. Good Detail

2.1.7.3.1. Other team members can understand changes

2.1.8. Documentation

2.1.8.1. API Documentation

2.1.8.1.1. This is what it does and how to call it

2.1.8.2. Repository Documentation

2.1.8.2.1. This is what it is meant to do

2.1.8.3. Added to repository

2.1.8.4. Committed and Pull Request

2.1.8.4.1. Reviewed

2.1.8.5. Markdown

2.1.9. At least TDD

2.2. Open Source

2.3. Libraries

2.3.1. Good Research

2.3.2. Using Popular and Supported ones

2.3.3. Prefer Open Source

2.3.4. Up to date

3. Infrastructure

3.1. Tidy

3.1.1. Redundant Stuff

3.1.1.1. Scripts

3.1.1.2. Environments

3.1.1.2.1. UI Dev

3.1.1.2.2. UAT

3.1.1.2.3. Dev

3.1.2. Consistency

3.1.2.1. Naming

3.1.2.1.1. Folders

3.1.2.1.2. Scripts

3.1.2.2. Location

3.1.2.2.1. Logs

3.1.2.2.2. Building

3.1.2.3. Similar Envrionments

3.1.2.3.1. Stage

3.1.2.3.2. Prod

3.2. Secure

3.2.1. Password Vault

3.2.2. ISO Stuff

3.3. Simple

3.3.1. e.g. Containers not in a VM

3.4. Reliable

3.4.1. 99.99% Uptime

3.4.2. Load Balancing

3.4.2.1. Scaling

3.4.3. Blue & Green setup

3.5. Understanding

3.5.1. Documentation

3.5.1.1. In Repoistories

3.5.2. Dev Engagement

4. Team

4.1. Empowered

4.1.1. Hiring & Firing

4.1.1.1. Knowledge & Skills

4.1.1.2. Engaged

4.1.2. Decisions

4.1.2.1. Code

4.1.2.2. Infrastructure

4.1.2.3. Standards

4.1.2.3.1. Commit Messages

4.1.2.4. Consensus Driven

4.2. Fun Events

4.2.1. Team Building

4.2.2. Hack Stuff

4.3. Safe Envrionment

4.3.1. Raise Concerns

4.3.2. Constructive Feedback

4.4. Training

4.5. Personal Development