Profile picture

Wade Naughton

Back-End Engineer
Open Resume Email Directly

About me

I'm hardworking, attentive to detail, and above all strive to be a considerate and communicative team member. I leveraged my background in customer service and database management as a springboard into backend development; as a developer I apply a user-based perspective that enhances the overall experience and usability of products.

I look forward to continuing to broaden my skillset and using my previous experience to become a dedicated member of the software community.

Preferred locations

  • Frederick, MD
  • Washington, DC
Open to other locations and/or remote work

Previous industries

  • Food & Beverages

Skills

  • GitHub
  • Heroku
  • PostgreSQL
  • Rails
  • RSpec
  • Ruby

Currently learning

None specified

Projects

Cuisine-Odyssey

Cuisine-Odyssey

Project scope time 40 hours
Collaborators

Tools Used

  • Atom
  • Bootstrap
  • Heroku
  • PostgreSQL
  • Rails
  • RSpec
  • Ruby
  • Software Architecture

Cuisine-Odyssey is an app that generates random recipes or random cocktails from around the globe, providing users the chance to spice up their dinner routine. This was a group project that consumed and created api endpoints and highlights the importance of microservice architecture. My primary responsibilities in this project were focused around setting up our backend microservice, creating endpoints, and utilizing activerecord to provide statistics to our frontend team. I also worked with Bootstrap on the frontend to provide our users a scaleable application.

Launch the App Code Repository
Screenshot detail for project  Cuisine-Odyssey
Screenshot thumbnail #1 for project  Cuisine-Odyssey Screenshot thumbnail #2 for project  Cuisine-Odyssey Screenshot thumbnail #3 for project  Cuisine-Odyssey Screenshot thumbnail #4 for project  Cuisine-Odyssey

sweater_weather

sweater_weather

Project scope time 30 hours
Collaborators

Tools Used

  • Atom
  • GitHub
  • Rails
  • RSpec
  • Ruby

A solo project that provides api endpoints to locate the current weather at a given location, as well as the weather at the destination of an imaginary road trip. The goal of this project was to consume three different third-party endpoints, and use that data to create the multiple endpoints that a frontend team could use to seamlessly find accurate information. This was the first time I practiced building an api endpoint that was dependent on more than one external api.

Code Repository
Screenshot detail for project sweater_weather
Screenshot thumbnail #1 for project sweater_weather Screenshot thumbnail #2 for project sweater_weather Screenshot thumbnail #3 for project sweater_weather Screenshot thumbnail #4 for project sweater_weather