Lecture Week 9

SUCCESS!!! I actually managed to take notes in one of Jason's lectures! Probably because he had them up on the screen but STILL, usually even then I can't keep up. So here they are...

How to approach new software...(According to Jason...)

1. Figure out what you want to do/have to do and find the easiest/best software to do so.

In all honesty, I don't usually even get to this stage. When it comes to computers I am very lazy, and I know I shouldn't be, but I figure that I want to be a writer, ergo I will hopefully not have to deal with TOO much new software post-Uni.

2. Realise what you think you want to do isn't what you should be doing. You don't know whats good or bad.

3. You've figured out you need something more advanced - how do you learn the software in a short space of time?

4. You can't. Good software is designed to be deep.

5. Begin by playing around- best way of beginning to learn.

I use this method. While it can be frustrating, I think it's a good way of avoiding being cliche. You can be innovative when you are playing around with new things, not knowing what they are supposed to do. I suppose this could also lead to picking up bad habits/becoming insanely confused, but in my experience, playing around with software is usually beneficial.

6. What are the common features of most software packages? Discern these, it's helpful.

7. SAVE YOUR WORK -A BILLION TIMES
SAVE YOUR WORK- under appropriate and easily remembered file names.

8. Try the help file of the software.

9. Typically the help file is crap. - still worth a try though!

Help files are actually so beyond crap. At least they are consistently unhelpful though. I like consistency.

10. Search it > best ways= ask a specific question.
Create/find a list of good sites to use to search. Use their search tool.

I did this last semester in Writing for the Web. There are so many good sites out there for help with programs like Dreamweaver. And if I can find them, anyone can find them, as I generally FAIL at searching.

11. Join forums - should guarantee you an answer eventually (keyword being EVENTUALLY). Make a dummy email a/c for forums. What d'you look for in a forum? How d'you know if it's good or bad? Check members, replies etc.

I have tried using forums... They are not for me. I don't have the patience. Admittedly, it's not often that I need help with software because I don't usually do anything new or download new software. Once again, I don't have the patience. Which is why I want to be a writer, i.e. I will hopefully never have to deal with figuring out software (wishful thinking, I know!).

12. Don't fear tutorial books/video tutorials but NEVER buy tutorial books.

As I think I've mentioned before, I work in a bookstore and since I did Writing for the Web last semester, I have been deterring people from buying tutorial books. They are ridiculous! Particularly the "for Dummies". They are SO filled with text, and I remember that in WritWeb, the only way I learnt properly was by the tutor showing me, then having me physically do it. I don't think it's something that many people could learn by reading about it.

13. Don't pay to take a course!

14. One of the main reasons to figure out software on your own - software is CONSTANTLY changing /updating.

Thankfully, this doesn't affect me much as I only use basic software to do basic things. It took me long enough to get used to Vista let alone other types of software.

It's all about content. >what you produce, i.e. make something that doesn't look like it was produced in a specific package. The easiest thing to do in software becomes cliche very quickly.