When you define yourself as an automation engineer, you are admitting to writing code. That comes with great responsibility: you should not just write code, you should write GOOD code.
You have handy tools and learning resources around to help you write tests that are easy to read, without much need for maintenance, clear and concise.
This talk will focus on how to make your code a star. I will go over some coding principles and best practices that will help you write clean code. The separation of concerns is just one of them. I will show the benefits of thinking like a developer, when it comes to the structuring of your test code. I will also show some of the tools, either from the IDE, or standalone, that highlight where your code can be improved, like: checkstyle, code review, automatic code inspections.
Lots of tips, ideas, dos, donts and examples are included.