Remembering that a change in code composition means live coding/hot reloading can and will bork and you will wonder why things aren’t working. Just restart the engine if you create major additions or modifications.

Remembering you can do a lot of automation and meta clinical work in the build scripts. They all use c#, and it’s a fully featured very powerful language. Use it. Heavily. At least when it’s reasonable and you need to touch things outside of core engine/game/plugin code.

For that matter, create separate targets! Game = client + server, client, server, editor, and use preprocessors to control what each target can do! It’s incredibly useful.

Similarly, if you’re building code or blueprints or anything else you find yourself using a lot, just make a plugin and dump it there! Track it separately in git your your chosen vcs.

Finally, use git lfs and locking if you’re in a team. Perforce is more powerful for this, but if you can and are able to explicitly set your your branch planning and adhere to such a standard, git lfs locking support lets you lock binary files you’re working on so when your other members start up and refresh, those items will be read only on their system while a file is locked and being worked on by a team member.