- Most of my analysis code is buried in other repositories, especially anything hosted on my Distill blog.
- Putting just the files necessary for each analysis in its own repo increases their ease of access.
- I avoid publishing code in the analysis posts I write.
- They are meant to be approachable by non-technical people.
- If you want to know how I built something in a post, this is where you can see how it was done.
- Most of what you see is a work in process.
- There is lots of code that generates outputs I have decided against publishing.
- If something seems out of place, I am likely still looking for a way to utilize it.
- I work on lots of things that I can't publish. Most of my work here are personal side-projects.
Seriously, just go to my portfolio, I explain them in detail there.
A tool to connect nonprofits in Baltimore City.
My work as a Principal Investigator in the Pro-Environmental Action Lab.
Do (protected) bike lanes make cyclists in New York City safer? Are they equitably distributed?
Is the MTA Subway system as bad as we think it is? Is it accurately presented by the MTA on public dashboards?
Playing around with animated map visualizations through Deck.gl bindings.