My workflow tends to be: - Build it in blueprints for rapid iteration - Port it to C++ for refactoring and long-term code quality I was bullish on the node b

My workflow tends to be: - Build it in blueprints for rapid iteration - Port it to C++ for refactoring and long-term code quality I was bullish on the node based programming, but over time I've liked it less and less. I've been a software engineer for 10+ years so I am very comfortable in the IDE and coding workflow. But yeah, discoverability in blueprints is out of this world. And the C++ classes use the same functions as the blueprint classes. Once you figure out how to find the C++ the blueprint is calling into, it becomes very productive.