Jacob Levernier, PhD
I am a software architect and senior developer specialized in facilitating data science. I work across computer science, applied statistics, privacy and data ethics, research design, and education – five pillars around which I set a ten-year goal while early in my career to develop both depth and breadth of knowledge.
I have worked as a senior-level developer, data scientist, software architect, and technical lead across a variety of domains, including healthcare, research libraries, and research nonprofits.
What is “facilitating data science”? I am at my best when creating infrastructure, tools, and workflows to answer questions generated by experts in a domain. My ideal work sits right between software development and data science – bringing substantive, data-analysis-aware experience to architecture and engineering decisions, and applying engineering best practices to data analysis.
This work could broadly be called “research software engineering” – helping experts to answer their questions, guiding projects to completion, from data pipeline generation, to platform creation, to model implementation, to privacy protection. I approach this type of work with a special emphasis on generating tools that empower users or colleagues who are not developers to conceptualize and answer subsequent questions themselves.
Recent Updates (posts and pages)(See all posts)
I welcome opportunities for collaboration. I also welcome messages from graduate students who are looking to exit academia. I’ve been through the process!
This website is titled Ad Unum Datum – In loose Latin, “Down to a single piece of data.”
I think that it is important to note that people’s reasoning, feeling, and opining change over time. Simultaneously, 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.
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.