Profile picture

Cameron Mackintosh

Software Engineer
Pronouns (he, him)
Open Resume Email Directly

About me

I remember very clearly the day I wrote my first lines of HTML on an eMac during my 7th grade IT class. I remember exactly where I was sitting in the computer lab, who the teacher was and the name of the student sitting right next to me. I remember the weeks that followed, and the ridiculous gif-addled websites I created for fun with my friends. I remember taking my projects home to work on them during my free-time.

Years passed and my interests shifted. After graduating from college, I spent 3 years in Anchorage, Alaska working as a digital producer and multimedia journalist for the state’s leading broadcast news team. Then I moved to Denver, Colorado and successfully pivoted to a sales/digital marketing role where I quickly became a top-performer on my team. After a lot of soul-searching and re-evaluating my career goals, I arrived at the Turing School of Software and Design. I have since rediscovered my childhood enthusiasm for coding, and I’m using that enthusiasm to fuel my transition to an exciting and fulfilling career in software engineering.

Preferred locations

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

Previous industries

  • Broadcast Media
  • Marketing and Advertising
  • Online Media
  • Public Relations and Communications
  • Research
  • Writing and Editing

Skills

  • CSS3
  • Express
  • Git
  • GitHub
  • Heroku
  • HTML5
  • JavaScript
  • Mocha
  • Node.js
  • Npm
  • PostgreSQL
  • Salesforce
  • User Experience Design / UX
  • User Interface Design / UI
  • Webpack

Currently learning

None specified

Projects

Bard Buddy

Bard Buddy

Contribution time 40 hours
Collaborators

Tools Used

  • Express
  • Node.js
  • PostgreSQL
  • React
  • Bard Buddy is a full stack web application that organizes and displays the complete works of William Shakespeare, allowing users to select and save passages from plays and poems line-by-line. This was a solo project completed in just under a week.
  • For this project we were asked to develop two different user personas and build our applications accordingly. Bard Buddy was designed as tool for high school and undergraduate students studying Shakespeare.
  • In addition to the front-end React application, I also built and deployed an accompanying backend by reworking a SQL database into an Express.js microservice.
  • I had little to no backend experience going into this project, so I'm immensely proud that I was able to build a functioning full stack application in just seven days. This required self-teaching PostgreSQL, as well as the challenge of dealing with a large amount of complex data.
  • At the same time, this project taught me some tough lessons about the value of simplicity and the peril of introducing unnecessary complexity to applications. Building a backend was not required for this project and was barely feasible in such a tight timeframe.
Launch the App Code Repository
Screenshot detail for project Bard Buddy
Screenshot thumbnail #1 for project Bard Buddy Screenshot thumbnail #2 for project Bard Buddy Screenshot thumbnail #3 for project Bard Buddy

metAPI

metAPI

Contribution time 30 hours
Collaborators

Tools Used

  • Node.js
  • React
  • TypeScript
  • Webpack
  • metAPI is a React application that allows developers to search through a database of public APIs based on categories such as Authorization, CORS etc. Users can also save APIs with accompanying notes to reference later.
  • For this project my team of 3 was asked to learn and implement one new language or technology. Because of our common interest in building scalable applications and using type checking to eliminate potential bugs during the early stages of development, we chose TypeScript.
  • Learning to use TypeScript was challenging. There are plenty of resources online about how to transition to TypeScript from vanilla JavaScript, but less information on how to use TypeScript in the specific context of React. Almost immediately, TypeScript assailed us with errors, creating a lot more work for us up front. But this paid off by preventing bugs as the project gradually took shape.
  • Throughout the project, our team maintained a strong collaborative environment, with a combination of paired programming and effectively divvying up areas of the project to complete asynchronously. We were also proud of the overall concept of our application - it was simple but solved an immediate problem. By providing our classmates with a link to the application we were even able to get some immediate feedback from our intended userbase, all of which was positive.
Launch the App Code Repository
Screenshot detail for project metAPI
Screenshot thumbnail #1 for project metAPI Screenshot thumbnail #2 for project metAPI

What's Cookin'

What's Cookin'

Contribution time 40 hours
Collaborators

Tools Used

  • CSS3
  • HTML5
  • JavaScript
  • Mocha
  • Npm

What's Cookin' is a recipe tracking / meal planning application that allows users to view their favorite recipes and plan shopping trips around them, similar to websites like All Recipes or New York Times Cooking. Inspiration for design and functionality was drawn from New York Times Cooking and similar designs found on Dribble.

Code Repository
Screenshot detail for project What's Cookin'
Screenshot thumbnail #1 for project What's Cookin' Screenshot thumbnail #2 for project What's Cookin' Screenshot thumbnail #3 for project What's Cookin' Screenshot thumbnail #4 for project What's Cookin'