I’ll set out here some newbie mistakes I made and the workarounds I utilised to get over some pretty basic hurdles.
I’m a visual learning kind of guy with a short attention span and I need to see fast, clear results. Basic syntax errors were my main challenge in starting out. I had to slow down and really check what code I had written.
The 'text101 course based learning' to create a simple game opened my mind to the potential of continuing with the overall learning programme.
In terms of early coding using C Sharp - being a little clumsy as a learner - the coding mistakes I found that I were making tended to be very basic typo based errors. Second guessing myself when I had actually understood the code requirement but failed to type it accurately was a common problem initially.
I had to take my time and very carefully check what I had typed was accurate.
I have found that you have to open yourself to the potential of these simple errors and when relaxed you will begin to ‘see’ the mistakes within the code.
Moving the screen formatting around in the C Sharp code within the Unity mono develop editor - remembering that whitespace is ignored by the computer when compiling really helps. Sometimes what was previously hidden becomes obvious to the eye. Reorganising the code let’s you review what you have written with fresh eyes.
As a visual artist I have sometimes rescaled a piece of artwork or looked at it upside down to 'see' the image with fresh eyes - not so easy with code.
The human brain makes up 80 percent of the image you see, so it’s a natural occurrence for mistakes to become invisible to the viewer.
Let's face it after a while with some fear of failure and some general frustration added in you just can't see the 'wood from the trees'.
It’s personally challenging to remember to look for the obvious mistake first before looking for the more complex solution. The build editor was returning ‘helpful’ error codes that sounded very complex but were really originating from missed brackets for instance.
Personally I was missing curly brackets randomly in the code and only through white space realignment on screen did this become obvious and easily remedied.
Yes the mono develop editor gives you build errors but this is challenging if you have no experience in interpretation of error readings and that your errors are typo randoms and not based on intelligent guesswork.
I also had to check myself as I was assuming too much about the structure of the game and the task to hand. This was a linear challenge set wisely to show the potential of key commands within the UNITY C Sharp editor. However enough content is there for anyone to begin to explore new ways of moving forward.
With great satisfaction I had an 'error free build' resulting in a simple text based game doing exactly what I understood it should be doing on screen - a very worthwhile result giving me the impetus to continue learning.
...use whitespace to get your head around where and what syntax is correct...
Hi, my name is Jamie, I'm a student on the Complete Unity Developer course and thanks to Ben and Brice I've made in-roads to coding that gives me the energy to keep going in terms of learning.
I thought I would join in the blog as I appreciate that different people will add in aspects of learning that might help others. Personally I got into difficulty with just basic typing and syntax issues which nearly stopped my progress as I was not going to post for help when I suspected I was doing something really basic preventing an error free build.