Skype Chat 6: Coding

Yesterday we were introduced to the intricacies of coding in java, by Paul Abbott, with a little html and css thrown in just for fun. It was difficult to follow at times, particularly juggling four different windows at one time, thank heavens for a large screen. It felt like having to catch four piglets and trying to put them into a shallow basket… with boxing gloves. However, I survived and took away some valuable ideas that will help me, particularly when I look at the video recording of the session again. These notions can be summarised in a very cursory way as:

  • Types of coded information are kept in discrete blocks.
  • One block of information tells another what to do and the different functions and variables in each one has to correspond to those in another block.
  • The process is like constructing a flow chart in your head. For that matter, drawing a flow chart when planning code is not such a bad idea. 
  • Brackets hold different types of information.
  • The syntax of the code has to be precise.
  • Practice by copying and pasting existing code and alter one parameter at a time and see what happens. Make sure all corresponding parts match one another. 
  • It is no good just reading about code, you have to do it as you go along to understand anything at all. 

I do not know how relevant coding is to my practice. It is immensely satisfying, though, when a piece of code works. I know from my scant experience with html and css. However, it is a totally different language and I struggle enough with words. So, although I may tinker with some code and perhaps even build a rudimentary something for the internet, I think I shall leave this one to those better suited for this activity. One thing, as Paul mentioned, it does help when you can converse in the same language with someone if you need something doing or collaborating on a given project.