Weeklies are due before the start of class on Thursdays. Starting week 2, your index page should have a section with a link to each weekly. Weekly P/F grades are posted here, if you want to dispute a P/F you are responsible for notifying the TA within two weeks.
Weekly #10: None
Focus on your final project!
Weekly #9 (Due 5/31)
- Read Rosa Menkman, Glitch Studies Manifesto
- Find one glitch (either on a screen or in the physical world), take a photo or screenshot of it, and post as your weekly response.
- Create a new HTML page to hold your ninth weekly response, and link to it from your index page.
- Browse through Rosa Menkman’s portfolio, and come to class prepared to discuss how it relates to the manifesto.
Weekly #8 (Due 5/24)
As you wrap up your data visualization and crowdsourcing projects, this week we reflect on the process of data collection.
- In class on 5/22, we’ll watch Mimi Onuoha, How We Became Machine Readable
- Read Adam Florin and Theodore Porter, The Greatest Number.
- Create a new HTML page to hold your eighth weekly response, and link to it from your index page. Reflect on what data is included or omitted from your Project 2, and in what ways you became more intimate with or distanced from the participants or subject by measuring, quantifying, or visualizing the data. Cite ideas from the video and reading in your response. Due end of day 5/24, rather than at the beginning of class.
Weekly #7 (Due 5/17)
This week, as you iterate on the design of your data project, we’ll look at some examples of data visualization.
- Browse through 3-5 visualizations as part of No Ceilings: The Full Participation Project, then choose two visualizations to focus on for a detailed analysis. (See the Explore the Data section on the homepage)
- Create a new HTML page to hold your seventh weekly response, and link to it from your index page. Link to the two visualizations you’ve selected and include some written analysis, using images to support your argument if needed. As you analyze, consider: How are color, typography, motion, and interactivity used to convey meaning? What is the author or creator’s point of view? Why might they have chosen to create a data visualization over another form? Where does the data come from, and what makes you believe the source is or isn’t reliable?
Weekly #6 (Due 5/10)
Next week, we’ll have a guest lecturer on Tuesday, Xin Xin, who will talk about networks and tools for encryption, privacy, and a more distributed web. As you read the articles, think about the various ways your data is tracked and stored online.
- Read Sarah Kessler, Think you can live offline without being tracked? Here’s what it takes and Jesse Kriss, Decentralization, Democracy, and Agency
- Create a new HTML page to hold your sixth weekly response, and link to it from your index page. Reflect on your experience learning about the tools presented in Tuesday’s lecture. Do you think you will use tools like these in the future? Why or why not?
Weekly #5 (Due 5/3)
This week reflects on design considerations for Application Programming Interfaces (APIs) in preparation for Project 2.
- Read Kin Lane, Politics of APIs and Tyler Singletary, Untangling the Politics of APIs.
- Create a new HTML page to hold your fifth weekly response, and link to it from your index page. Find an API that you find interesting for any reason and describe what you or others might build with it. What information does it make available? What can you do with it? What are the politics in the API you’ve chosen?
Weekly #4 (Due 4/26)
This week, as you design your portfolios or website, the readings are about internet aesthetics and alternatives. Consider these in contrast with Frank Chimero’s essay from week 1.
- Read Nick Douglas, It’s Supposed to Look Like Shit: The Internet Ugly Aesthetic and Olia Lialina, Rich User Experience, UX and Desktopization of War.
- Create a new HTML page to hold your fourth weekly response, and link to it from your index page. Post one image that you find in one of your own social media feeds (Snapchat, Instagram, Tumblr, etc) that you consider “ugly” and one that you consider “beautiful”. Choose your own definition of these terms based on the readings and your own thoughts on the subject.
Weekly #3 (Due 4/19)
This week reflects on themes of network surveillance and identity online. While you are thinking about your portfolio/websites, consider how you would like to be seen. What do you want to highlight, what do you want to keep private?
- Read one of these: Joanne McNeil – The Dream Must Be Continuous, Sydette Harry – Everyone Watches, Nobody Sees: How Black Women Disrupt Surveillance Theory, Ashe Dryden – Social Networking as Peer Surveillance.
- Create a new HTML page to hold your third weekly response, and link to it from your index page. Write two good questions for discussion, reflecting on the themes of the articles.
Weekly #2 (Due 4/12)
- Read Frank Chimero, What Screens Want.
- Design and style your index page, and updating it to hold links to all of your work this semester. Upload it to your DMA webspace, replacing your page from last week. From now on, post all of your assignments—both projects and weeklies—linking from this page.
- Create an additional HTML page for your second weekly response and link to it from your index page.
- Weekly response: Take an internet dérive through at least five links. Post the five links with a couple sentences that frame the journey by explaining the links relationship to each other.
Weekly #1 (Due 4/5)
Create a placeholder COMING SOON or UNDER CONSTRUCTION index.html with some text and an animated GIF on the page using this template. Just edit the paragraph text and replace the image for now; we’ll spend more time on styling next week!
- Upload the index.html file to your DMA webspace using Cyberduck or another FTP client of your choice. (See How to FTP for instructions)
- Add the link to your placeholder page to this spreadsheet, so that it can be added to our class page.
Check that your image has been uploaded correctly by visiting your site at http://users.dma.ucla.edu/~yourusername/ (“yourusername” is what you use to log into support.dma.ucla.edu and the DMA cloud)