Re:A Software Engineer’s Guide to Unity and AR/VR Developmen...
by amadeusw on Friday May 12, 2017 @07:48PM
(#14328819)
Are these issues easily fixed by refactoring?
As a newcomer to Unity, I'm ok writing poorly performing quick code to experiment, and properly implement the code at a later stage. I'm afraid that I may burn out too quickly if my first interaction with a platform is too much concerned with patterns.
[ Parent
| on HN ]
Re:A Software Engineer’s Guide to Unity and AR/VR Developmen...
by Impossible on Friday May 12, 2017 @07:56PM
(#14328845)
They are easily fixed with a refactor, but many of the solutions are either easier to implement or not much more difficult to implement than the example code.
Re:A Software Engineer’s Guide to Unity and AR/VR Developmen...
by delphinius81 on Saturday May 13, 2017 @12:59PM
(#14331859)
Can be fixed with a refactor, but it's best to not get sucked into these bad habits at all. If you are learning, might as well learn how to do things the right way from the beginning.
Hooking up references to GameObjects and Components through the editor is some of the Unity "magic sauce." You should be doing things that way, or by hooking things up once during Awake/Start.