Profile picture

James McHugh

Back End Engineer
Pronouns he/him
Open Resume Email Directly

About me

After a successful career as a musician in Los Angeles, I decided to pivot and make a fresh start as a software developer. I bring a detail-oriented work ethic and highly communicative style of collaboration to any team. During my time at Turing, I developed a strong foundation in object oriented programming and test driven development. I have a good deal of experience building REST APIs and relational databases, as well as a solid foundation in building out frontend apps - using JavaScript, CSS, and Bootstrap. I'm currently open to work and would love the opportunity to contribute to a team, as well as continually learning to become a more well-rounded developer.

Preferred locations

  • Los Angeles, CA
Open to other locations and/or remote work

Previous industries

  • Music

Skills

  • ActiveRecord
  • Adobe Premiere Pro
  • Bootstrap
  • Git
  • GitHub
  • GitHub Projects
  • Google
  • Heroku
  • LinkedIn
  • Miro
  • PostgreSQL
  • Postman
  • Rails
  • RSpec
  • Ruby
  • Slack
  • SQL

Currently learning

  • Go
  • Golang
  • Python

Projects

oompr

oompr

Project scope time 80 hours
Collaborators Profile picture for Zach Bergman Profile picture for Rodrigo Chavez

Tools Used

  • ActiveRecord
  • Bootstrap
  • CSS3
  • GitHub
  • GitHub Projects
  • Heroku
  • HTML5
  • JavaScript
  • Miro
  • PostgreSQL
  • Rails
  • Ruby

Oompr is an idea I pitched for the Mod 3 Consultancy Project. It is an acronym for "Out of My Price Range". The basic concept of the app was for "real estate window shopping" - people love to look at beautiful, expensive homes. In addition to a fantasy browsing feature where users could search luxury real estate listings in their area, I also implemented a "reality check" button where users would entered their estimated monthly income and the results would filter to show them only listings that they could actually afford. I worked as the backend anchor and built the whole backend API from scratch. We had a small 3 person team and used a simple two-app service oriented architecture to also support a front end rails app which used JavaScript, CSS, and Bootstrap to create a professional-looking, mobile-friendly app.

Code Repository
Screenshot detail for project oompr
Screenshot thumbnail #1 for project oompr Screenshot thumbnail #2 for project oompr

TurLink

TurLink

Project scope time 80 hours
Collaborators Profile picture for Noah Durbin Profile picture for Lance Butler Jr Profile picture for Luis Aparicio Profile picture for Reese Green Profile picture for Kim Ewing Profile picture for David Swatzell Profile picture for Zach Wolek

Tools Used

  • ActiveRecord
  • CSS3
  • DevOps
  • Docker
  • GitHub
  • GitHub Projects
  • Heroku
  • HTML5
  • JavaScript
  • PostgreSQL
  • Rails
  • React
  • RSpec
  • Ruby
  • Slack
  • Software Architecture
  • TypeScript

For my Mod 4 Capstone, I was part of a pilot project where we built a link shortener for the Turing community. I was part of a sub-team of 2 people that built the backend Rails app, and we collaborated with a total of 8 team members over the course of 4 weeks. As part of the backend Rails team, I was responsible for building the database and the backend API. We worked closely with the frontend team to expose endpoints they needed in order to built the basic MVP for logging in, shortening links, and exploring popular links.

Code Repository
Screenshot detail for project TurLink
Screenshot thumbnail #1 for project TurLink Screenshot thumbnail #2 for project TurLink Screenshot thumbnail #3 for project TurLink