Car Maintenance App

New app in progress! Hopefully it won’t take months to complete. Should be pretty simple. Especially since this app is going to be primarily for me - and I’m not going to worry too too much about the UI elements. Thinking this is going to be primarily a django based app with templates and model-based views like the keys app. Current State: Developing database models Purpose Provide myself and whoever wants it a place to track their car maintenance, and to make sure that they know when the next scheduled service for a particular maintenance item is due. [Read More]

Google .dev Domains, GitHub Pages, and Heroku Apps

How to get things wired up now that you have that sweet, sweet .dev domain name

At the end of February 2019, Google released general access to the .dev top level domain. I had heard about this happening about a year ago, and am now the happy owner of two .dev domains! One of these is chasesawyer.dev and will soon be the new home of this site! But how to get it set up? When you buy a domain name, nothing is really set up for them - going to those addresses doesn’t point to anything Firefox and Google will just say “Server not found. [Read More]

RTTApp

A Solution for Tracking Repair Tasks

Repair Task Tracker RTT is a full stack app that addresses the needs of a computer hardware management process, allowing the tracking and resolution of issues/problems with the hardware, as well as the configuration and components of each major hardware item. RTT is meant to be a back-of-house tool, replacing paper tickets and spreadsheets. The goal of this project was to implement a GraphQL app, with useful data, allowing a seamless user experience as they operate through the app, and data is downloaded and uploaded in the background. [Read More]

KeysApp

A Solution for Tracking Brass Keys

The Keys App was my first major project that sought to solve a problem with managing key checkouts without requiring a cumbersome customer database / sign up form. This would target an institution that mostly catered to internal customers, such as a university’s AV department and it’s instructors. It largely replicates a paper-form-based system, with an added layer of data validation and control (emails, phone numbers must be in a valid format; keys can only be returned by their original owners; keys can’t be checked out twice; etc. [Read More]