Skip to content
Avatar
noelworden/README.md

Noel Worden

A full-stack software engineer with a backend focus

Contact

| Email | Blog | Github | LinkedIn |

(917) 513-1753

Tech Stack

Elixir/Phoenix | Ecto | SQL | Postrgres | HTML | CSS | React | Typescript | Javascript | git | Docker | Ruby/Rails | Vim | Agile Development | Java | Bash | Photoshop

Working Experience

Software Engineer | MojoTech | May 2018 - Present

  • Integrated 2FA process into existing React/Typescript registration/login user flow
  • Client so pleased with solo work they modified their contracting protocols to allow for future solo engagements
  • Led the onboarding of new junior engineer into her first project
  • Part of greenfield project utilizing Elixir/Phoenix with Ecto and heavy SQL to build accounting software for credit card processing client
  • Overhauled existing Elixir/Phoenix application with new authorization library
  • Helped implement multi-step online claim process for an insurance client using React/Typescript
  • Progressively shorter ramp-up times when starting projects with new languages

Junior Full-Stack Engineer | Canvas United | January 2017 - April 2018

  • Created Rails-based CMS platforms
  • Greenfield projects as well as existing client maintenance and upgrades
  • Used Photoshop to optimize source images of photo-heavy content to decrease average page load time by 80%
  • Refactored legacy monolith to allow for re-use of promotions functionality for new business use cases
  • Part of the Canvas portfolio site rebuild, utilizing Contentful and Netlify

Cabinetmaker | Hanleys Woodworking | August 2013 - December 2016

Lead Digital Imaging Technician | Versatile Studios NYC | March 2012 - July 2013

Freelance Digital Imaging Technician | Freelance | July 2008 - September 2012

Education

Bloc | Mentor-enhanced online web development education | February 2016 - December 2016

Minneapolis College of Art & Design | BFA - Photography | August 2004 - December 2007

Pinned

  1. Angling Atlas

    Elixir

  2. 1
    * Why standardize messages? Its clean. Easy to see what changed and when. As an up-and-coming developer, my repos will probably be potential employers first impressions of me. Clean code (proper indentions/spacing etc) and formatted commit messages help show that I care about my code. 
    2
    
                  
    3
    * The workflow is to create a `.txt` file as a template, and configure git to use that file as the default message when commiting.  
    4
    
                  
    5
    * The key is the character count. Note the dashed lines representing 50 characters for the summary, and 72 for the description.

86 contributions in the last year

Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Mon Wed Fri

Contribution activity

September 2020

Created a pull request in noelworden/atlas that received 1 comment

[TOOL] Remove unused dependencies

There are a handful of dependencies that are not being used. Might be a mistake to remove them, but only commented them out, so they can easily be …

+62 −68 1 comment

Created an issue in noelworden/atlas that received 2 comments

Establish hosting services

start by looking at this doc -> https://hexdocs.pm/phoenix/deployment.html Gugalixir specific -> https://hexdocs.pm/phoenix/gigalixir.html Gigalixir

2 comments

Seeing something unexpected? Take a look at the GitHub profile guide.

You can’t perform that action at this time.