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.

Lessons learned as a software engineer working at appear.in

436 views

Published on

Presentation of my talk at Agile Tour Lithuania (Kaunas and Vilnius)

Published in: Software
  • Be the first to comment

Lessons learned as a software engineer working at appear.in

  1. 1. Lessons learned as a software engineer working at Walmyr Filho 1
  2. 2. 2
  3. 3. A little bit about 3
  4. 4. A little bit about.me/walmyr-filho 4
  5. 5. Let’s go to what matters 5
  6. 6. Lesson 1 6
  7. 7. Automate everything you can benefit from 7
  8. 8. Jest Slack bots Selenium Protractor ESLint Terraform Applitools Tape Mocha GoCD 8
  9. 9. Lesson 2 9
  10. 10. Use linting rules to enforce best practices 10
  11. 11. $ npm run lint 7:55 error Strings must use doublequote quotes 7:5 error Expected indentation of 4 spaces but found 2 indent 8:7 error 'foo' is assigned a value but never used no-unused-vars 24:34 error Missing semicolon semi 56:53 error Unexpected function expression prefer-arrow-callback 11
  12. 12. Lesson 3 12
  13. 13. Code review is a very good way to improve coding skills 13
  14. 14. 14
  15. 15. Lesson 4 15
  16. 16. Run experiments 16
  17. 17. https://appear.in/foobarbaz?widescreen 17
  18. 18. Lesson 5 18
  19. 19. Learn and apply new technologies 19
  20. 20. From ES5 to ES6 20
  21. 21. Lesson 6 21
  22. 22. Interoperability tests 22
  23. 23. 23
  24. 24. Lesson 7 24
  25. 25. Infrastructure as code 25
  26. 26. 26
  27. 27. Lesson 8 27
  28. 28. Work on small things 28
  29. 29. - Avoid conflicts - Quick feedback during code review - Deliver frequently - Show results - Fail fast & learn 29
  30. 30. Lesson 9 30
  31. 31. Refactor without mercy 31
  32. 32. - Code improvements - Improve readability - Make code cleaner - Ease maintainability - Care about your teammates 32
  33. 33. Lesson 10 33
  34. 34. Pipelines as code 34
  35. 35. pipelines: foobar: group: foobarbaz materials: foobar-master: git: git@github.com :foo/bar.git branch: master stages: deploy: approval: manual job: deploy-foobar tasks: exec: command: sh arguments: foobar.sh 35
  36. 36. Summarizing 1. Automate everything you can benefit from 2. Use linting rules to enforce best practices 3. Code review is a very good way to improve coding skills 4. Run experiments 5. Learn and apply new technologies 6. Care about interoperability tests 7. Use infrastructure as code 8. Work on small things 9. Refactor without mercy 10. Create pipelines as code 36
  37. 37. Thanks! 37
  38. 38. Questions? 38
  39. 39. Lessons learned as a software engineer working at Walmyr Filho about.me/walmyr-filho 39

×