Profile picture

Matt Holmes

Back End Engineer
Pronouns he/him
Open Resume Email Directly

About me

My experience as a paramedic and an experiential program manager have equipped me with the skills to successfully join a software development team. The need to both plan ahead and to be prepared to respond to emerging situations dynamically are second nature to me. Because I enjoy working with others on a team, finding opportunities to cultivate relationships with my coworkers is important for finding connection. My goal is to help support people's quality of life through software.

I love to build custom functionality for the kind of applications that used to have pain points when I used them as a consumer. I am interested in the scalability of tech solutions to long-standing problems. Organizations that implement company values in a way that builds up their employees and customers are especially attractive to me.

Preferred locations

  • Denver, CO
Open to other locations and/or remote work

Previous industries

  • Medical Practice
  • Program Development

Skills

  • Atom
  • Bootstrap
  • Git
  • GitHub
  • Heroku
  • PostgreSQL
  • Rails
  • Redis
  • RSpec
  • Ruby

Currently learning

  • JavaScript

Projects

Do Goodr

Do Goodr

Project scope time 60 hours
Collaborators Profile picture for Ted Staros Profile picture for Michele Comfort Profile picture for Colgan Meanor Profile picture for Adam Burgess

Tools Used

  • Git
  • GitHub
  • Heroku
  • PostgreSQL
  • Rails
  • Redis
  • Redux
  • RSpec
  • Ruby
  • SQL

Do Goodr Backend is a back-end application that exposes an API to support the user-facing application which allows individuals to find volunteer opportunities within their area. The exposed API will allow front-end developers to display users, organizations and events. Users will be able to search via zip code.

The goal of this project was to deploy a service-oriented architecture to expose an API that would satisfy the front-end team’s requirements.

Main functional accomplishments: Expose an API for CRUD functionality. Expose an API that uses an external API and internal logic to filter by distance. Utilize background workers to send confimatory emails to users. Develop additional functions that support future application growth.

Launch the App Code Repository
Screenshot detail for project Do Goodr

Komodo

Komodo

Project scope time 80 hours
Collaborators Profile picture for Micha Bernhard Profile picture for Jacob Yarborough Profile picture for Haewon Jeon Profile picture for Stephanie Helm

Tools Used

  • Bootstrap
  • Continuous Integration
  • Git
  • GitHub
  • Heroku
  • JavaScript
  • PostgreSQL
  • Rails
  • Redis
  • RSpec
  • Ruby
  • User Authentication

Komodo is a harm-reduction application for individuals who use drugs alone. The specific danger of overdose could be mitigated by having an automated timer that the user can de-activate if they are okay. Komodo lets a client create emergency contacts and start a timer when they are about to use a substance. If the timer is not stopped before it runs out, it will text their contacts with the client's address, map and other information pre-created by the client.

Using separate frontend and backend applications (which required exposing our own API), our application fulfilled its design goals. Some of successfully-implemented aspects of this project included consuming MapQuest and Twilio APIs, implementing background workers with Sidekiq and Redis, and a continuous integration pipeline with CircleCI and Heroku. Early and consistent abstraction and encapsulation allowed us to easily port our backend API to a new Heroku application when our original went down minutes before a presentation.

Launch the App Code Repository
Screenshot detail for project Komodo