q1and2.txt

1. git

branches, commits, remotes

opening pull requests

code reviewed by someone 

environments => prod, dev and staging

talk about staging => https://dev.to/flippedcoding/difference-between-development-stage-and-production-d0p

2. quality software

https://en.wikipedia.org/wiki/Software_quality

security => if you use rails you get built in security features like csrf protection

reliability => convention over configuration, following best practises and not having to reinvent the wheel, OOP best practise, solid principles, error handling 

efficiency => speed of your algorithms, optimise queries, network speed, how large the files you're sending, blocking and non blocking code

maintainability => best practises, making your code modular, ensuring that you have good documentation, DRY principle, technical debt https://en.wikipedia.org/wiki/Technical_debt, good commit messages, testing

portability => cross platform, not tied to one thing

size => caring about file size, using things like assets pipeline or webpack to ensure your assets are as small as possible and will therefore load faster

testable => writing code that can be tested, for example if you're using global variables it's basically impossible to test something, one method does one thing