John Bragg Email and Phone Number

As the first employee of Arch, I got to set everything up from scratch. I set up the entire environment, from the development environment using Garden to orchestrate local Kubernetes services with hot-reloading to easy deployments of production environments using Garden, Terraform and Azure. Every engineer at Arch took turns on deploy duty, and all engineers could deploy to any environment in a matter of minutes. The system used my custom db schema management tool (albatross) and my nodejs-based API server (based on Koa2).I single-handedly built their home heat load estimation system, home room/zone layout deduction engine, home data reconciliation system, HVAC equipment database, equipment output capacity deduction engine, interactive map UI, database architecture, infrastructure architecture, deployment pipeline and many, many other systems.

Took a year or so to pursue an idea in the drone/3d mapping space.The product was fully streamlined, using Garden to deploy all services and infrastructure to Kubernetes on Azure. Backend services were built in Node/Typescript with data stored, modified and retrieved via SQL functions built into PostgreSQL using a custom-built SQL-based database structure migration system. SQL triggers were used for all asynchronous processing of data and side-effects using BullMQ for job management and processing. Deploys to staging and production environments and code verification (tests, security analysis) were triggered via GitHub actions. The development environment allows for hot-reloading of all services and data structure migrations (using a rollback to base state, then remigrate to new state approach, custom-built also).The product itself used mapping UI via Mapbox with many custom controls and overlays, with parcel data provided by Regrid APIs and 3d reconstructions efficiently integrated into the 3d GL-based base map.Mapping and reconstruction was accomplished via drone with RTK FIX-correlated data using ODM triggered via imagery upload in the UI. The models themselves were compressed and simplified for efficient transfer to the browser, and base orthomosaic maps were overlaid on top of the Mapbox-provided maps.

Opal brought me in to help modernize and streamline their several-years-old product and codebase. I very quickly found many ways to update, upgrade, and modularize the product and the codebase. Over the next 2 years or so, we did all of these things I documented, splitting the code into services, upgrading the frontend to React, containerizing, Dockerizing, then Kube-izing (?) the entire system, implementing front-end component and style libraries, moving to a monorepo with a singular build and deployment pipeline, in-housing all external dependencies to vendors, and many other smaller upgrades and added features. This allowed us to sign on customers who needed a self-hosted system due to the severed external dependencies and possibility to host the entire system on any container-based system. This allowed the design and development teams to work in concert on implementing standard component and style-consistent UI. This also allowed the company to start using Elixir and other backend technologies easily via services.

For most of my tenure at Seed, I was the entirety of the web/frontend team. I was tasked with delivering the same output as a larger team, so I found ways to modularize systems into packages, parceling out pieces that could be worked on by other engineers in other roles, designers, and copy writers (everyone else). A few systems I developed to help with this:- styles.seed.co - A styleguide of sorts, showcasing some of the reusable styles exposed by my styles package that can be included in any other system to provide colors, typographic styles, reusable animations, and many other variables and mixins. Our designer did most of the updating and maintenance of this package himself after it was implemented.- forms.seed.co - Another styleguide showcasing my reusable forms package. This exposes many types of common inputs and other components that can be used in any other system to provide a consistent experience. It also exposes reusable primitives for Form components, Stepper components, Input Blocks, Alerts, SVG Icons, and many collections of controls that act as a single input (ex. Address input).- seed-base - A private package that provides the "chrome" for any application at seed. It provides all of the login/logout and session management functionality, the header and user menu controls, alerting, and base actions for use in many other contexts. This has allowed us to build many applications on the Seed platform quickly, with a huge amount of reuse of code.I worked very closely with our design team (another team of one) to ensure a consistent and reusable style and feel throughout all Seed systems. This saved us a ton of time in manual design review (consistency is expected between apps/screens) and a ton of my time by allowing him to do much of what he needed to do himself. All apps at Seed were ES6 using React and Flux, with immutable data storage, and a standard API client library. Deployments were done via Webpack and S3, and served with CloudFront.

Circle brought me in to quickly stand up their MyCircle content portal that acts as a backstop for filtered content (if your destination is filtered, you are redirected to this content site). We wanted to build an application that would communicate directly with the local circle device to cater content to the device being filtered. To do this, we came up with a protocol for finding and communicating with the local device over http to download a personalized configuration for the content in the application, as well as statistics and usage meters for different types of content and site. The site is live, and in for the most part the same shape as I left it, at http://my.meetcircle.com/ (though it doesn't do much without a Circle device). The content of the site was pulled from a myriad of categorized sources and streamed to the browser via web sockets, so any customer would always have a never-ending, always-something-new stream of content to enjoy when they could not reach their intended destination.The portal uses React and Flux for it's data and display binding, statically compiled with Webpack, and Node/Express on the backend side.

My partner and I started Cozy after I moved to San Francisco from Mountain View, and saw the need for a modern tool for renters and landlords to communicate and do business with. At the time, we were running our design firm, so we worked on it on the side until we decided the idea had merit enough to start talking to VCs. We shut down the design firm and focused wholly on Cozy after a short while, and after raising our first round of funding, and those subsequent, ended up with a 20-person team of mostly engineers and designers, building a well-received and well-used product that has started to evolve renting in the US as it grows and picks up speed.The first version of the product was developed mostly by me and one other engineer, and over time, I saw the company and its product evolve and refactor into a microservice-based API fronted by a static Knockout/Require-based frontend written to be modular and future-proof.

Ground-up site designs and implementations as well as maintenance of our large portfolio of hospitality industry web sites. Helping the Design Team move forward in standards compliance and emerging technologies such as AJAX and advanced CSS and Javascript techniques and technologies.

I call this my first retirement. Ask me about it!

Firewall Engineer for a while, then on the Penetration Testing Team for a while.