Check-ins: name, how you’re doing, a win for this week
Announcements
Quiz
Go through quiz answers and discuss
Checking your work
Documenting your work and GitHub
Break
AI policy revisited
Workshop - what do you want people to take away from your visuals?
Lab time
Week ahead
Check out
Office hours this week: By appointment?
Last coding notebook assignment is posted. It’s not a coding notebook, though :)
The rest of your assignments will all feed into requirements for your final story.
Name one of the functions used in R to convert columns to rows or vice versa. (3 pts)
Name two strategies for reducing the clutter, or chart junk, on a graphic. (4 pts)
Name at least one reason why you would want to get your data fully prepared in R before uploading to Datawrapper/Flourish? (2 pts)
If you used both Datawrapper and Flourish, did you like one or other better? If you only used one, why did you pick that one? (1 pt)
Your strategy for a data check will depend on a few things:
How complicated your analysis is
The stakes of your story
Who you have available to you
Commenting your code is key
Force yourself to really examine what each line does, both in terms of the logic and if the code is accurate for what you’re trying to do
Try to replicate the analysis another way - some people will do using another programming language, or you could use Excel
Let go of defenses and ego as you and/or a friend/colleague are going through it
Your methodology should explain the logic (when not obvious) of the steps you took, as well as potentially outlining those steps.
Your methodology can live in multiple places / have multiple layers:
In the text of the story (good for: if needed for your audience to understand your findings)
In a box at the bottom of the story (good for: if it’s relatively brief, or if there are things pretty important for a general audience person to know)
In a ReadMe file on GitHub (good for: if it’s more involved, it you don’t have a good way to include on the page, or if only highly specialized readers would want to know the details)
In the comment of your code (good for: the details, or if you want others to be able to use and adapt your code. Generally NOT sufficient by itself)
Examples of code commenting and methodology
GitHub is used for lots of things, tailored for web developers. We will focus on:
setting up a GitHub
setting up a Repository (read: folder for a project, even though they have another product actually called project)
Decoding Climate Change: Unlocking the Power of Programming for Data Journalism