mark|ellis

about me

Hi, I'm Mark.

By day, I'm a software engineer based in Clutch City, and I build applications for the web, mostly with Javascript. Mostly.

Outside of work, I write poetry, prose, and screenplays, build games, and collaborate with friends to make music and films. I also take an embarrassing number of photos of my dog, Gatsby, and can quote nearly all of Jurassic Park.

projects

The classic game of luck and logic, but with the ability to design and share custom minefields! Designed as a serverless application, with a Node backend API deployed on Heroku, and a React client-side application deployed with Now.

A responsive React/Redux wedding RSVP program using Google’s Sheets API to turn a Google Drive spreadsheet into a free database. This project also needed to support i10n, since my wife’s family only speaks Spanish.

→ Guided transition of several legacy applications to modern web stacks, and increased their test coverage from 0% to > 75%; → contributed to establishment of standards and best practices used across LOB-wide front-end teams, including linting, automatic code formatting, testing, and code design patterns; → developed and maintained firm-specific application bootstrapping scripts, forked from react-scripts; → supervised team of 3 UI engineers.

→ Led frontend development in a small squad of remote engineers focused on delivering modern, scalable, standards-compliant, responsive web-apps. → Implemented new client-side architecture and build setup using React, Redux, and Webpack that enabled faster development and component reuse. → Resolved 50% of documented UI bugs within a month of joining the team.

→ Contributed to development of a boilerplate template based on newly implemented tech stack that decreased the time-to-productivity for new developers. → Worked closely with UX and Design teams to rapidly prototype and pitch proof-of-concepts for new products. → Helped extract common UI components into an internally-shared component library. → Leveraged Webpack to reduce average build time and CPU usage by 87.5% and 93%, respectively.