Who is Jeremy Friesen?
Part recluse and part old-school geek, I cut my teeth programming by dutifully transcribing monospaced computer code from a magazine onto our venerable Atari 64K. Ever focused on helping others, I enjoy using tools from my problem-solving tool belt as well as learning new ones. Sometimes I wish I had a cape, but not the kind that get caught in engine turbines nor the ones that are ironically hip. And maybe I’d like a mask too.
Since starting my programming career in 1998, I’ve worked on:
- Proprietary insurance billing and collection software.
- Document management systems for contracts, addendum, and other legal documents.
- Health and life insurance quoting and renewal software. (mma-online.org)
- Database-driven e-commerce (cardcare.com, postycards.com)
- Developing custom content management and legacy data integration (www1.ccs.k12.in.us)
- Conductor, a custom Content Management System for the University of Notre Dame
- map.nd.edu, a Google maps layer for Notre Dame
What do you do at Notre Dame? What’s so cool about that?
Application development; I’ve worked on developing and maintaining the server-side element of various University Communications applications (conductor.nd.edu, map.nd.edu, admissionschat.nd.edu). Building from the Hydra project, I’m working on Digital Library initiatives with a focus on preservation and discovery.
What do you do in your down time?
I spend time with my wonderful wife, three children and step-daughter; listening to children playing, cleaning, gardening, practicing music, reading, drawing, writing, playing games and providing a taxi service. During “my time” I play pen and paper role-playing games with my friends…collaboratively narrating stories. I also enjoy blogging about my take on rules (as they apply to games).
What did you dream you would do when you were a kid?
I dreamed I would build things with people. I was an avid Lego builder and collector. My friends and I would often collaboratively build and vicariously inhabit these tiny geometric worlds.
How did it come about that you work at Notre Dame?
By helping another AgencyND developer, Erik Runyon, fix a failing automated test. Prior to that, I was (and still am) a regular participant in a programming user group that had its first meetings in Grace 500, a place that later became my office.