I’ve found that they’ve become relatively stable, however there are for sure some pitfalls and things you need to consider.
Never rename your project after having coded workflows / source files and having them in templates just doesn’t really work properly (cause the project name changes).
Always always make a constructor in a coded source file. If you don’t have a constructor in a coded source file they Studio can and will freak out at you at some point.
Even if its an empty constructor, make one.
After that, maybe you can be more specific on any issues and some of us can share tips for how we work around it or if we do things differently to not hit it.
@AlvinStanescu its easy to get only negative feedback. Let me say, the coded source files in particular are my absolute favourite new feature of the past several years as its soooo good to make my own classes now rather than having to deal with gross endless dictionaries or JObjects and the coded workflows work super nice for cross platform high code stuff, I’ve been using them more and more for my test cases also.