Modern team workflow

An overview of our current web development workflow at Mirego. Subject to change since we're always trying to improve this workflow.

Transcript

1. Modern team development. @garno OpenCode XXIII Overused fonts for a presentation u say?
 Gimme a break.
2. An awesome team. <3
3. Benefits?
4. benefits. less bugs accelerated on boarding process increased productivity easier human resource transfer blame the team, not the person Reduced stress maximum fun better overview of what is going on
5. Git flow our
6. Simple feature git flow. feature/simple-one master
7. complex feature git flow. master feature/complex-one feature/complex-one- -step-one feature/complex-one- -step-two
8. Pull request? Always!
9. pull requests. Anatomy of a pull request A title A Description A BRANCH Some commits
10. pull requests. Anatomy of a GOOD pull request A clear and concise title A passing spec A « why » description A next step (optional) A branch name respecting GIt flow A screenshot (optional) An animated gif (optional) A ISSUE tracking number (optional)
11. Anatomy of a BAD pull request pull requests. A shitty title No Context No description too much additions & deletions a weird branch name Anatomy of a BAD pull request
12. Always? YUP! pull requests. never make sneaky fixes
13. Coding style. = Consistency.
14. coding style. my code, your code, it should not matter. my style, your style, it should not matter. Its our code. Its our style.
15. coding style. « Phare looks into your files and check for coding style errors. » https://github.com/mirego/phare
16. coding style. No shameful error no useless comments no time wasting optimize review time on the logic, not the syntax.
17. coding style. Demo.
18. Respect, is everything.
19. Easy deployment for everyone
20. easy deployment. Everyone should be able to deploy it should not be hard You should not have to search for credentials THE migrations should be known
21. easy deployment. « Hanzo is a sharp tool to handle deployments in multiple environments on Heroku. » https://github.com/mirego/hanzo
22. easy deployment. it should not be hard hanzo deploy [environment] hanzo deploy qa hanzo deploy staging hanzo deploy production
23. easy deployment. Everyone should be able to deploy Even managers are deploying!
24. easy deployment. You should not have to search for credentials .heroku-remotes
25. easy deployment. THE migrations should be known UPGRADE.md
26. Tips
27. tips. TRAVIS CI
28. tips. DUMMY DATA rake db:reset dummy_data:create
29. Benefits?
30. benefits. less bugs accelerated on boarding process increased productivity easier human resource transfer blame the team, not the person Reduced stress maximum fun better overview of what is going on
31. big thanks, happy development.