• Due: assessed in three phases:
    1. 24 Jun
    2. 26 Aug
    3. 4 Nov
  • Mark weighting: 20% total
  • Submission: fortnightly, via Teams (see below)
  • Policies: see the policies page


An audiovisual diary is a way for artists/musicians to keep track of ideas and notes for use in future projects. It could be a paper book with, a blog, or personal website. Artists as diverse as Leonardo da Vinci, Frida Kahlo, and Kurt Cobain all kept visual diaries.

Every other week, you will be required to take a bit of time outside of class to write about a piece of code art/code music you made in class and post this to your creative code blog—it’s your audiovisual diary. You’ll be using MS Teams as the platform for your audio visual diary. In EXTN1019 we call it an audio visual diary rather than just a visual diary, because we’ll be looking at code music and code visuals over the two-year duration of the course. You can find the exact dates on the main deliverables page.

We expect you to actively engage with the content we deliver during the weekly workshops in this course. The creative computing blog allows you to practice this content regularly as you develop your own style; just as any artist or musician would. On the weeks your blog posts are due, we will give you a provocation ahead of time in the workshop material. Provocations are like written prompts or open-ended questions. They should be thought of as “jumping off points” for exploring a question or idea in your code sketches. Your task with each blog post is to create a a code_sketch which explores this provocation during the workshop and write a short description about the what you made to post on the Teams channel.

Submission Process

For each topic we cover in class, we either want you to create your own sketch based on a provocation we set in class, or extend some starter code we provide in class. In either case, we want you to create at least one creative code sketch and discuss the process you took to develope your sketch.

Here’s the process for completing your blog post:

  1. Develop your sketch, either in class or outside of class. Your sketch should either explore a provocation we give you in class or use (and modify) some example code we give you in class

  2. It’s not compulsory, but you are encourage to explore variations of what you implemented.

  3. Take a screenshot or screen recording of the sketch(es) you wish to submit

  4. Make a post in the MS Teams CC blog channel. You should include your screenshots/screen recordings, the blog number e.g. “Blog 3” and a short description of your work and process. The text component of the blog should include:

  • a short description of your sketches
  • any sources of inspiration
  • a discussion of the process you adopted to implement your idea

Marking criteria

As discussed at the top of this page, your creative code blog (i.e. your Teams post and class discussion in small groups) make up 20% of your overall mark for this course and there are 10 blog submissions in total. These are marked in three stages over the course of the year.

The marking criteria are:

  • clarity of communication in your post descriptions

  • critical engagement with the specific topic, starter-code or provocation associated with the blog submission

  • reflection on your creative process


So what’s the point of the visual diary?

The point is to practice sketching with code and also engage with the creative code community i.e. the works of other creative code artists and musicians. In the early stages of the course, the sketches will focus on a specific concept we have covered in class.

I’m new to this whole artistic thing, and I’m a bit worried what other students might say about the stuff I’ve chosen—what should I do?

EXTN1019 is a caring place where we’re all at different stages of our learning journey. In general everybody is positive and nurturing to everybody else.

If you ever feel belittled or made to feel like you don’t belong by a classmate or a teachers, then let the course convenor know privately and I’ll make sure it doesn’t happen again.

How “polished” does my code art have to be?

We do not expect your code art to be very polished - they are sketches after all and they can be rough implementations. This activity is about practising and not refining.

How long does the text component of the blog post have to be?

There is no hard word limit, but approx. 300 words.

Do I need to make a post in the very first week?

No. The first post is due in Week 3.

When are the blog posts “due”?

Well, as stated above, you need to make a post every other week, and it’s due fortnighyly on Fridays at 11:59pm. The first blog post is due on Friday May 13th at 11:59pm.

Do I need to include images/videos of my sketches for the blog?

Yes - either screenshots or short screen recordings (30-50 seconds).

Can I work on it during the workshop?

Yes! Every other week, we will be dedicating the workshops for making your own code art with the concept we introduced the week before. So if you create something during the workshop which you want to include in your blog post, then by all means include it. You’re also welcome to use time outside of class to work on the blog.

How long should I spend on this every week?

I’d say that you could probably knock it over in an hour or so if you put your head down and get it done. You can obviously spend as long as you like, but if it’s taking you 10+ hours a week you’re probably over-thinking it :)

Can I use open-source code for my blog post?

Yes, for sure – as long as you provide links to any code that you used and you make some interesting changes/additions of your own to the code. You can include the link to the open-source code at the bottom of your blog post.

Can I use other artists’ work as inspiration for my sketches?

I don’t see why not :) You can absolutely look for sources of inspiration and reference them in your blog post (name of inpso/artist, name of work, link to work). However it’s not part of the marking criteria.

When will I get my marks & feedback?

As mentioned above, the blog posts will be marked in three stages. You should receive your mark and feedback 1-2 weeks after each deadline.

bars search caret-down plus minus arrow-right times arrow-up creative-commons creative-commons-by creative-commons-nc creative-commons-sa