Skip to content

Commit

Permalink
Merge branch 'drafts'
Browse files Browse the repository at this point in the history
  • Loading branch information
camille-s committed Feb 16, 2024
2 parents 41e3db5 + b296c4c commit d63379d
Show file tree
Hide file tree
Showing 2 changed files with 30 additions and 1 deletion.
27 changes: 27 additions & 0 deletions decision_checklist.qmd
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
---
title: "Decisionmaking checklist"
---

When you're planning out your own work, it's important to make conscious decisions about what you're doing and why. I keep saying this, but one of the things I dislike the most about no-code visualization products like Excel or Tableau is that they encourage you to *not* make these decisions, but to just rely on defaults or automated suggestions.

In contrast to just going with defaults, you as a thoughtful visualization practitioner should go through the decisions you *could* make in order to determine what decisions you *should* make. This is something you do in your EDA process, as well as in sketching charts on paper.

It's also useful for understanding a chart someone else made, whether just to read it, or to revise or critique it.

## Checklist

What decisions could be / should be / were made about...

* what data to include
* what data to exclude
* what visual encodings to use
* what types of scales to use (sequential, qualitative, diverging)
* what to put on the x- and y-axes
* how to scale the x- and y-axes
* how to use color
* how to use text
* how to use annotations
* where to draw attention
* what conclusion to suggest

What have I forgotten from this list?
4 changes: 3 additions & 1 deletion weeks/05_good_code.qmd
Original file line number Diff line number Diff line change
Expand Up @@ -119,7 +119,8 @@ cool_project
°--utils # misc scripts & bits of data to use throughout the project
```

## Build tools
:::{.callout-note}
## An aside: build tools

Build tools are outside the scope of this class, but for larger projects especially or projects that will need to be updated over time, they'll save you a lot of headaches. I have some projects that I rebuild once a year when new ACS data comes out, and I've got things down to where I can make one or two calls on the command line flagging the year as a variable, and all the data wrangling and analyses are ready to go. In fact, this site rebuilds from a frozen list of packages every time I push to GitHub, and if that build is successful, it publishes automatically.

Expand All @@ -130,3 +131,4 @@ Some tools I use:
- [GitHub actions](https://github.com/features/actions), including ones specifically for [R](https://github.com/r-lib/actions/)
- [Docker](https://www.docker.com/), build a small isolated environment for your projects, some designed for [R](https://github.com/rocker-org/rocker-versioned2)
- Package & environment managers: [mamba](https://mamba.readthedocs.io) or [conda](https://docs.conda.io/en/latest/) for Python, [renv](https://rstudio.github.io/renv/) for R
:::

0 comments on commit d63379d

Please sign in to comment.