Sure. I'd say be aware of code smell as you write and read your own code. Look out for functions that have too many parameters.as they're probably doing too much. Avoid passing data to a function that it doesn't absolutely need. Be careful about returning complex variables. Don't write functions that do more than one thing. Avoid globals and closures. In general, functional style programming will naturally lead to better separation of concerns.
If you are using a class based programming language, determining what must be a class member function versus a pure function helps with separation of concerns at the interface design stage.
An example of the above with C# might be determining what is a class member function versus an extension method.
Tell others that you are particularly insterested in growing in this area before they review your code when you submit it, or ask someone to review code you have already written with this in mind.
