I designed and developed public-facing web applications for small businesses in Utah County. Most were simply informational applications with a CMS for the business owner(s) to modify their own content. In addition I developed two social media applications for a couple clients and they were rather large in scope.I worked for myself for several years before I met my wife and decided to enter the corporate world where I could depend on a steady paycheck and enjoy valuable health benefits. My biggest surprise when entering the corporate world was finding out that all my fears about being behind on technology, standards, etc were totally unfounded. In fact, in many areas I was still ahead of the curve; without even trying I had stayed up to date on all the latest languages, frameworks, coding standards, etc.The only things I had to learn from scratch were collaborative tools like source control and continuous integration with a build server. That's the point when I finally started to realize that this industry is where I belong and it's what I understand. Figuring out that you're one of the good players in a space is a particularly exciting realization!I have kept Chevtek around all throughout my career and it has been extremely useful in acquiring new skills as I apply them to new projects.

At SunPower I was able to leverage my industry knowledge and experience to spearhead a brand new 3D design application as a project lead. It was a great experience working with Babylon.js, developing new skills in graphics and 3D game engines. It also provided an opportunity to really dive into state machines, the solution we settled on to solve an increasing complexity problem where so many events were happening that coordinating them all became nearly impossible. State machines allowed us to visualize the application in any given state and reason together as a team to refine what actions are allowed in each application state. The app was a great success and I'm excited to bring those new skills with me to a new opportunity!

SunRun has a positive atmosphere with a variety of apps and systems to maintain. SunRun merged with Vivint Solar in 2021 and provided many challenges for the tech teams as we worked tirelessly to merge and update SunRun systems with the knowledge and tech we brought with us from Vivint Solar. It has been a very enlightening experience.

Vivint Solar has been a great place to work. It has a positive atmosphere and all of our apps are kept up to date with the latest (but stable) tech. We are a node.js shop utilizing document stores like MongoDB, CouchDB, etc. We rely heavily on services provided by AWS such as Lambda, Elastic Beanstalk, DynamoDB, and more. Our front-end experiences are powered by Angular, React, and Vue across a multitude of internal and external web apps.

I worked as part of the front-end team for Adobe Analytics. My team was a brand new team focused solely on the front-end using tools such as AngularJS, jQuery, LESS, etc. We even dabbled in some back-end tech such as node.js. Though I was part of the front-end team, it was inevitable that I had to modify a fair amount of PHP on the back-end.

My team was responsible for maintaining an internal web application used only by employees as well as a public-facing web application seen by customers. Both applications were developed in ASP.NET Webforms/MVC.The most noteworthy project that I spearheaded was called KLAS Report Microsites (KRMS). We took their primary product (PDF reports containing data on medical software) and we brought it all online. Before KRMS KLAS would publish static PDF files to their web server and their customers would pay for and download these reports. It was a very archaic and opaque way of handling this data, which is the lifeblood of KLAS Research.I had an idea to create a front-end framework that would load a report into the browser viewport dynamically. It would find which of our customized HTML templates was associated with the report, then it would iterate through the template locating special CSS classes on "editable" elements in the template and it would populate those elements with custom data that was entered by the reporting team (the team that creates and publishes the final reports).These elements are the areas that the reporting team could modify themselves using an internal interface that we developed for easily creating and modifying reports. The only part of the final process that needed to include the IT team was the creation of new markup templates, which had to be designed specially for the report viewer plugin. Each editable element would specify what kind of "editor" it should open in a modal dialog when clicked; this gave the reporting team a lot of control over their reports.With the addition of all sorts of analytics hooks into these reports KLAS was given insight into so much more about the user experience. They can now track things like how long a user viewed a report, what areas of the report they viewed, etc etc. It was an extremely fun project and I was very proud of it when it launched. It went off without a hitch!