[Geo]Data is my professional portfolio, blog, and repository of self-made tutorials. Here, I will make connections between all things GIS and data, while focusing on these areas: (1) automation, (2) reproducibility, (3) software development and data engineering, (4) geospatial data science, and (5) business intelligence.
Jordan Frey
I’m a software engineer with a background in geospatial data science and a strong advocate for event-driven, microservice architectures. I develop data-centric and production-ready applications primarily with Python, SQL, bash, Terraform, and increasingly GoLang in all major cloud environments (AWS, GCP, and Azure). I’m primarily interested in automating data pipelines, DevOps, and backend development.
What I Do
I started out making maps and analyzing spatial data in R, and over time my work shifted toward the systems that surround that analysis. Today I work as a senior engineer on the DevOps, MLOps, and AI side of a data platform, after several years as a data engineer and technical lead.
The kinds of problems I’m usually working on are:
- Event-driven data pipelines: asynchronous, horizontally-scalable ETL/ELT pipelines that extract, validate, transform, and export data, with dead letter handling.
- Cloud infrastructure: Terraform, Kubernetes deployments, CI/CD, autoscaling, cloud monitoring, cluster and repository migrations.
- Shared tooling for engineering teams: reusable Python packages, Terraform modules, pipeline templates and Helm charts
- MLOps: tracking and evaluating the accuracy and reproducibility of LLM-powered applications.
Education
I obtained my Master’s degree (2020) in Geographic Information Science from Clark University in Worcester, MA. I have a Certificate of Advanced Study (2018) in Data Science from Syracuse University, and obtained my Bachelor’s degree (2015) in Environmental Studies from Ithaca College.
AI Disclosure
This blog is by and large hand-typed, and both its content and structure is 100% driven by me. All posts have been molded around past experiences and desire to write them down for posterity. By taking the time to elucidate my own understanding of a technical concept, I am able to further solidify and deepen that knowledge for myself. While AI is used as a personal learning assistant and editor, in no way shape or form does AI drive the content or style in the blog. Every post continues to take hours of my own human time to piece together, verify, and edit, just as it did before the advent of AI.