The document outlines ten lessons learned as a software engineer, emphasizing the importance of automation, linting rules, code reviews, and applying new technologies. It highlights practices such as working on small features, frequent delivery, and refactoring code for maintainability. Additionally, it mentions the significance of using infrastructure as code and creating pipelines as code.

1. Lessons learned as a software
engineer working at
Walmyr Filho

3. A little bit about

4. A little bit
about.me/walmyr-filho

5. Let’s go to what matters

6. Lesson 1

7. Automate everything
you can benefit from

9. Lesson 2

10. Use linting rules
to enforce best practices

11. $ npm run lint
7:55 error Strings must use doublequote
quotes
7:5 error Expected indentation of 8 spaces
but found 4 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

12. Lesson 3

13. Code review is a very good
way to improve coding skills

15. Lesson 4

16. Run experiments

17. https://appear.in/foobarbaz?widescreen

18. Lesson 5

19. Learn and apply
new technologies

20. From ES5 to ES6

21. Lesson 6

22. Interoperability tests

24. Lesson 7

25. Infrastructure as code

27. Lesson 8

28. Work on small things

29. - Avoid conflicts
- Quick feedback during code review
- Deliver frequently
- Show results
- Fail fast & learn

30. Lesson 9

31. Refactor without mercy

32. - Code improvements
- Improve readability
- Make code cleaner
- Ease maintainability
- Care about your teammates

33. Lesson 10

34. Pipelines as code

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

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

37. Thanks!

38. Questions?

39. Lessons learned as a software
engineer working at
Walmyr Filho
about.me/walmyr-filho