Hi, I'm Dave! I build tools and applications to help people get stuff done
Who I am
- Father and Husband
- US Marine Veteran
- 70% Software Developer, 30% UX Advisor
What I do
I build software and tools to help people solve problems accurately and efficiently. In between coding, I also serve as an in-house “UX advisor”, teaching options and patterns for building human-friendly workflows, services and user interfaces to dev teams.
My Background
I spent most of my high school years building web sites and implementing my own CMS'es and other critical-type stuff (e.g., recoloring MSIE scrollbars in CSS), continuing this process through graduation and until I enlisted in the military.
At every duty station I was “that kid with the computers”, helping peers and supervisors fix technical headaches of all sizes, especially data issues: manual and automated conversion of “Excel spreadsheet databases” scattered across sharedrives; defining storage and backup procedures for critical data; and documenting those processes and training those who would inherit those new systems.
In the background of my military career, I continued working towards my undergraduate degree in computer science which I was able to complete a year before my enlistment ended. Upon leaving the military, I got my first official software development job.
Two years into the development business, I began looking for a way to be more deliberate about building effective and approachable applications for users rather than just having good UX happen by random chance. Armed with my shiny new GI Bill, I pursued and completed my graduate degree in information architecture and user experience, the fields which govern how to arrange and present structured and unstructured information and workflows in ways that are intuitive and easily understood by end users and not just the folks who build them.
What is the purpose of this site?
Much of the career advice I've read from people I respect in the software development field trends toward the sentiment that all developers should have a blog. The one that most sticks out in my mind is this blog post by Scott Hanselman.