Ad Unum Datum

“Down to a single piece of data.”

Data science means having one’s feet firmly in several disciplines – not only to do one’s work competently, and even innovatively, but also to recognize one’s social responsibility and thus also innovate ethically.

I am a data scientist and data ethicist; I have a passion for creative, sustainable analysis and governance, founded firmly in principles from social science.

Curriculum Vitae

My current CV, which includes my publication and presentation history, is available in PDF format.

Recent Posts

More Posts

I’ve written several suggestions for facilitating addressing pain points in conference calls, after reading and experimenting for six months.


The (free, open-source) org-checkbox extension is now available in the Visual Studio Marketplace for creating color-coded todo lists.


I’ve developed what I think is a novel User Interface approach for embedding a list of Frequently Asked Questions into a dense document, using a straightforward markup strategy.


Having taken part this week in a panel discussion at the 2017 DLF Forum conference, I raise a question I’ve been struggling with: can users consent to data mining, if they can’t realistically be expected to substantively understand the risks?


Earlier this week, I presented as part of a panel discussion at the 2017 DLF Forum conference. I am releasing my slides and speaking notes for that presentation.


Recent & Upcoming Talks

Cartography and Code: Incorporating Automation in the Comparison of Medieval Toponyms Across Maps
May 16, 2018 1:30 PM
Introduction to Python for Humanists
May 10, 2018 10:00 AM

Teaching & Mentorship

I have taught statistics and data analysis, including Bayesian modeling, to undergraduate and graduate students; been invited to develop curricula on programming, psychometrics, data visualization, and data science for graduate students and professional staff; and am part of collaborative pedagogy organizations Software Carpentry and Data Carpentry.

My teaching and mentorship philosophy centers on building collaborative spaces where it feels acceptable and even celebrated to not know, repeatedly and often, and to build incrementally through that into expertise. I believe that in settings of collaboration and support, accepting the vulnerability of having to find or build answers yields deeper insight as knowledge is gained through iterative practice.


  • Python for Humanists (2 days, Curriculum author and sole instructor), Price Lab for Digital Humanities, University of Pennsylvania, 2017, 2018.
  • “Non-Psychometric Survey Design, Or, Creating Surveys that Measure what you Actually Want to Measure” (1.5 hours), The Wharton School Customer Analytics Initiative, University of Pennsylvania, 2017.
  • Data Visualization Best Practices (1.5 hours), The Wharton School Customer Analytics Initiative, University of Pennsylvania, Mar. 2017, Aug. 2017. In collaboration with Manuel de la Cruz Gutierrez, PhD
  • Software Carpentry workshop (1 day, Bash, Python), Price Lab for Digital Humanities, University of Pennsylvania 2017.
  • Python for Humanists (3 days), Price Lab for Digital Humanities, University of Pennsylvania, 2017.
  • Project Management best practices (1 hour), CLIR Postdoctoral Program webinar, 2017. In collaboration with Kieran Healy, PhD
  • “Building Book Scanners without Breaking the Bank” (1.5 hours), introduction to hardware engineering and software availability for creating document and book scanners
    • Ms. Fembot un-conference event, sponsored by the Fembot Collective and Ms. magazine, University of Southern California Annenberg School for Communication and Journalism, 2016
    • Digital Scholarship Center, University of Oregon, 2015
  • R for Librarians in the Humanities” (3 hours), Digital Scholarship Center, University of Oregon, 2015
  • “An introduction to R for the Digital Humanities” (1 hour), Digital Scholarship Center, University of Oregon, 2015
  • “Time Travel for Academics: Get Your Digital Life in Order, and Protect Yourself from Yourself” (one hour), introduction to version control with Git
    • University of San Francisco (Psychology), 2015
    • University of Oregon Methods Laboratory (Psychology, Biology, and Neuroscience), 2015

Lecturing and Instructing

  • Graduate Student Python Learning Group (Lecturer, Mentor), University of Pennsylvania Libraries and Price Lab for Digital Humanities, Jan. 2018 - Present
  • R Learning Group (Administrator, Lecturer), University of Pennsylvania Libraries, 2017 - Present
  • Advanced Data Analysis (512 Course number, for graduate and Honors undergraduate students), University of Oregon, 2015, 2016
  • Research Methods, University of Oregon, 2012, 2014, 2015, 2016; University of San Francisco, 2011
  • Graduate Statistics (612 Course Number), University of Oregon, 2015
  • Guest Lecturer on Bayesian Modeling, Graduate Statistics (612 Course number), University of Oregon, 2014, 2015
  • Bayesian Modeling in R Club (Co-Founder, Administrator, Lecturer), University of Oregon, Jan. 2014 - June 2014
  • Moral Development, Child Development, University of Oregon, 2012, 2013
  • Motivation, Emotions, and Personality Traits, University of Oregon, 2011
  • Writing, St. Ignatius Institute, University of San Francisco, 2009


  • The Children's Hospital of Philadelphia
    Department of Biomedical and Health Informatics
    2716 South Street
    Philadelphia, PA 19146

The Scope of this Website

I think that it is important to note that people’s reasoning, feeling, and opining change over time. Orthogonal to these changes, people’s vocabularies, their ability to describe and express their thoughts and feelings, develop over time. These facts are obvious, but are not always acknowledged in public discourse. Even personality, while largely stable, can change over time.

Thus, please keep in mind that almost everything that I express on this website is date-stamped; my words may not be the same, or even similar, to those that I would use to discuss a topic today.

On a similar note, AD·VNVM·DATVM is my personal website. I am not speaking for my employer or collaborators when I write here.

If you are the original owner of any work that’s hosted on this website and believe that it’s not being used in a way that complies with Fair Use principles, please contact me.

Short bits of code that do not have a license attached to them (e.g., snippets of CSS) are for you to use without feeling like you need to give credit (although it’s always nice): See the CC0 license. More substantive bits of code may have alternative (non-CC0) license notes attached to them, usually in their headers.

Any text not otherwise cited is © Jacob Levernier and released under a Creative Commons BY license. If you would like to use it in some other way, though, feel free to contact me to arrange a different license.

I’ve used this much text to describe license terms because I am a proponent of best practices for data and code management, and because I worry that leaving legally-relevant expectations ambiguous can lead to one or both parties in an interaction (here, the author and the user) feeling cheated. When someone authors or otherwise creates code, icons, or other types of content, and says it’s “free,” it’s often unclear what “free” means (Does “free” mean that I can use it, but need to provide a link back to the author’s website? Does it mean that I can use it as long as I’m not profiting off of its use?). It’s even more problematic when an author states that something is “free to use,” but has an “All Rights Reserved” notice at the bottom of the page (those two statements are potentially at odds with one another). Thus, in contrast to some who purposely leave their work unlicensed, I prefer to make all copyright and license terms as explicit as possible.

The Technology behind this Website

This website is created using blogdown, an RMarkdown-enabled integration of Hugo. It also uses the MIT-licensed Hugo Academic theme.

Search on this website is powered by DuckDuckGo, an alternative search engine to Google, which does not track its users in the ways that Google does.

The header of this website uses Particle.js to render flowing networks of points.

Image Credits

I keep an up-to-date list of image and other credits.