Development Practices
haritha[dot]harikumar[at]prometeon[dot]com
When you write code...
-
READABLE code
- meaningful variable names
- break into functions
- add documentation
- Always LINT
- Build API endpoints compatible with mandate
- Always TEST your code
- Follow BEST SECURITY practices when handling config details
- Always LOG
- COMMUNITY SUPPORTED and LATEST libraries
Secure Coding...
- Use OAuth for Authentication & Security for Internal Application
- Underlying technology behind system should be abstracted
- Code & Use API's wisely
- Use API's to expose larger volumes of Data
- GET API's should never change DB state
- Expose only required Data
- Expose data considering permissions
- Validating every data that comes from external sources
- Handle Errors following HTTP Codes
Containers are best friends...
There are 2 ways to implement and run an application
-
In your system
- install every single library in system
- Slow down your machine :/
-
Using containers
- creating virtual spaces with required libraries.
- Independent from your system
- Easy to use in any OS
- Security
Using Git...
- Every Project should be instantiated with Git
- Create a new branch for every new feature or issue & work on that branch
- Commit often
- Write meaningful commits
Meet Gitlab/Github...
- Every project should have a Gitlab or Github repo associated
- Every project should have a Readme.md file
- For every feature create an issue that explains the feature
- For every issue create a Merge Request or Pull Request that shows your changes.
Need to Document...
- API Documentation
- Inline Documentation
- Specifically for functions or logic
- Project Documentation
- Readme.md file in gitlab/github
- contains all necessary commands
- Issue Documentation
- Made in Gitlab/Github incase you have a feature to implement
Development Practices
By haritha28
Development Practices
- 351