Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Improve your workflow
development, continuous integration, deployment
Adam Štipák | @new_POPE | adam@rekurzia.sk
Who I am?
● full stack developer (since 2006)
● Sven Creative
● Sygic
● Diagnose.me
● and other “secret” projects
What is the problem?
Manual work
is so slooow!
Solution?!
automate!
automate!!
automate!!!
Nice! But when? Where? How?
● as soon as possible
● as much as possible
● from save source code up to production
1. development
Install a project
2 (3) commands (git clone, install, run)
or use
Save the source code
Editors have an autosave.
PHPStorm
Task runners
play for YOU!
“auto refresh”
“Time-saving synchronised browser testing.”
http://www.browsersync.io/
Conclusion
1. save the code
2. do work
3. autorefresh
4. profit!
2. continuous integration
Team player
repeat, repeat, repeat ...
Builds
“deployable package”
Build process
1. on every push to repository (every branch)
2. static code analysis
3. install dependencies (libs, package...
Process assets
Run tests
Publish build result
3. deployments
Simple, simple, simple
best deployment = automatic deployment
Friday is a weekday, not “no deployment” day
Deployment is not the end...
Monitor it...
Monitoring
Conclusion
Tools are here.
So use it.
Thanks
Adam Štipák | @new_POPE | adam@rekurzia.sk
Upcoming SlideShare
Loading in …5
×

Improve your workflow

356 views

Published on

Some usefull tricks & tips how you can improve workflow from development up to production.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Improve your workflow

  1. 1. Improve your workflow development, continuous integration, deployment Adam Štipák | @new_POPE | adam@rekurzia.sk
  2. 2. Who I am? ● full stack developer (since 2006) ● Sven Creative ● Sygic ● Diagnose.me ● and other “secret” projects
  3. 3. What is the problem? Manual work is so slooow!
  4. 4. Solution?! automate! automate!! automate!!!
  5. 5. Nice! But when? Where? How? ● as soon as possible ● as much as possible ● from save source code up to production
  6. 6. 1. development
  7. 7. Install a project 2 (3) commands (git clone, install, run) or use
  8. 8. Save the source code Editors have an autosave. PHPStorm
  9. 9. Task runners play for YOU!
  10. 10. “auto refresh” “Time-saving synchronised browser testing.” http://www.browsersync.io/
  11. 11. Conclusion 1. save the code 2. do work 3. autorefresh 4. profit!
  12. 12. 2. continuous integration
  13. 13. Team player repeat, repeat, repeat ...
  14. 14. Builds “deployable package”
  15. 15. Build process 1. on every push to repository (every branch) 2. static code analysis 3. install dependencies (libs, packages) 4. setup DB (migrations) 5. process assets (JS, CSS, images) 6. run tests 7. publish results
  16. 16. Process assets
  17. 17. Run tests
  18. 18. Publish build result
  19. 19. 3. deployments
  20. 20. Simple, simple, simple best deployment = automatic deployment Friday is a weekday, not “no deployment” day
  21. 21. Deployment is not the end... Monitor it...
  22. 22. Monitoring
  23. 23. Conclusion Tools are here. So use it.
  24. 24. Thanks Adam Štipák | @new_POPE | adam@rekurzia.sk

×