Coding Together - A Dev Workflow
3 likes1,227 views
This document summarizes a Dev Workflow that progresses from a solo developer workflow to incorporating teams and continuous integration practices. It begins with the downsides of a solo workflow like stress and lack of source control/deployment processes. It then shows how small teams improve workflow but still lack aspects like asynchronous production and scalability. The document advocates for leveraging libraries, version control, continuous integration, code reviews and deployment systems to facilitate large team "big team workflows" with features branches, testing environments and quality assurance practices.
More Related Content
What's hot (20)
Viewers also liked (16)
Similar to Coding Together - A Dev Workflow (20)
![Conversational Development [Agile Portugal]](https://cdn.slidesharecdn.com/ss_thumbnails/agilept-180529111109-thumbnail.jpg?width=560&fit=bounds)
Recently uploaded (20)
Coding Together - A Dev Workflow
- 1. A Dev Workflow CODING TOGETHER Peter Chester @peterchester // tri.be
- 9. Deploy.
- 10. Deployments should be BORING(Save your energy for the afterparty!)
- 11. How did we get here?
- 13. development strategy account management project management quality assurance support sales design finance operations
- 14. Benefits of the Bachelor • Control • Low Overhead (and High Profits) • Competitive • Efficient
- 15. the Price of Freedom • Stressful & Exhausting • Scatterbrain Syndrome • Quality Assurance • It’s lonely.
- 16. I had a simple workflow.
- 17. Codinglikeit’s Customer’s need is fulfilled Review with customer Deploy code (FTP) Test locally Write code Translate to scope Customer states a need 1999
- 18. What’s missing from the solo workflow? Customer’s need is fulfilled Review with customer Deploy code (FTP) Test locally Write code Translate to scope Customer states a need
- 19. • Source Control • Deployment Process • Dev Site What’s missing from the solo workflow? Customer’s need is fulfilled Review with customer Deploy code (FTP) Test locally Write code Translate to scope Customer states a need
- 20. Youth is bad for your health.
- 21. • Late nights • Hairy releases • Tiny fonts • Giant functions • A general disdain for wellness Youth is bad for your health.
- 23. Then there was a baby
- 25. Maybe I need a team.
- 27. • Share the load • Inspire & Educate • Smarter than me • Income stability Teams are Awesome!
- 29. • Communication • Efficiency • Scale Teams are Expensive!
- 30. Deploy code Customer’s need is fulfilledCustomer’s need is fulfilled Review with customerReview with customer Deploy code Test locally Write code Translate to scopeTranslate to scope Customer states a needCustomer states a needSmallteam workflow Developer
- 31. Deploy code Customer’s need is fulfilledCustomer’s need is fulfilled Review with customerReview with customer Deploy code Test locally Write code Translate to scopeTranslate to scope Customer states a needCustomer states a needSmallteam workflow Team Lead Developer
- 32. Deploy code Customer’s need is fulfilled Review with customer Test locally Write code Translate to scope Customer states a needSmallteam workflow Developer
- 33. Deploy code Test locally Write code QA Developer Smallteam workflow Test on dev server Push to origin/develop Test locally Write code
- 34. Deploy code Test locally Write code QA Developer Smallteam workflow Test on dev server Push to origin/develop Test locally Write code Version Control Dev Server Deployment Process
- 35. Deploy code Test on dev server Push to origin/develop Test locally Write code What’s missing from the small team workflow?
- 36. Deploy code Test on dev server Push to origin/develop Test locally Write code • Asynchronous production • Code quality • Scalability What’s missing from the small team workflow?
- 38. BIGteam workflow CI Server Developer QA Dev #2 Post-release smoke test Tag Pull Request “merge” Code review Run automated tests Create Pull Request Push to Origin Write code Create feature branch Deploy! Pre-release smoke test Run automated tests Delete feature branch Merge Test feature branch
- 39. Into the Sausage Factory
- 40. Conscious Coding
- 41. Code unto others as you would have them code unto you.
- 42. Code for your future self
- 46. Code for is for people
- 47. Poem to a PC 1000101101011011010010101001110101010010101101
- 48. Architecture
- 49. • Files • Functions • Classes • Variables Nomenclature QUACK!
- 51. Short summary Clearly named Class Clearly named variables Succinct documentation Unambiguous function titles
- 52. • WP-CLI • ACF or CMB2 • SASS or LESS • Grunt or Gulp • … Leverage Libraries
- 54. Version Control
- 57. Gitflow Workflow THANK YOU TO VINCENT DRIESSEN AND ATLASSIAN HOT FIX RELEASE FEATURE DEVELOP MASTER
- 59. • Central (Redmine) • Jira • Asana • Trac Use a Ticketing System
- 60. • PHPLint • Unit Testing • Integration Testing • API Integrations & Automation • Deployments Continuous Integration
- 61. • Consistency • Quality • Learning Code Reviews
- 64. Remote Deployment Tool Capistrano or Rocketeer
- 65. Continuous Integration Deployment Snap CI, Circle CI, Codeship
- 66. Dev Sites
- 69. Branch based testing sites
- 73. Production Dev Production Production HOT FIX RELEASE FEATURE DEVELOP MASTER Dev Dev
- 74. Pick-n-pull
- 75. Pick-n-pull
- 79. Ticket Testing
- 80. Smoke Testing
- 81. Deploy.
- 82. Deploy.
- 83. Q&A Peter Chester @peterchester // tri.be