Hi, I'm Aaron
I write software for fun and profit. I like creating. I like delivering. Shipping maintainable software that helps people makes me happy. I believe in developing software confidently. I prefer to define automated specifications of system behavior before I write implementation. I prefer to build features from the outside-in-- starting with the highest level of interaction and working my way down. I believe in using the right tools for the right job. I believe it is better to be a problem solver than a <%= popular_technology %> expert. I believe that interpersonal skills are a requisite part of a development toolbox. Effective communication, conflict resolution, self and team awareness are as essential to success as a solid technical foundation. I enjoy working in collaborative environments and function best on small, cross-functional teams.
Design Effective Interviews
Conducting an interview is difficult. How well can you expect to know someone after a few hours of interaction? This is why it’s important to optimize the time spent speaking with a candidate. I’ve conducted interviews for a variety of roles: Software Developers, Customer Support Representatives, Development Managers. I’ve had the opporunity to speak with dozens of candidates. I’ve made my fair share of mistakes – asked the wrong questions, pressed a topic too hard, or lacked significant information or preparation to conducting the interview. Each interview provides an opporunity for me to hone my skills and better understand the responsibility – to company and candidate – of an interviewer.
Raspberry Pi Temperature Sensor
A few weeks ago, I purchased a Raspberry Pi. After reading Eben Upton’s Raspberry Pi User Guide, particularly the two chapters on which he focuses attention on the GPIO, I had an idea for my first project. The post covers the first iteration of a home temperature monitoring project I put together using a Raspberry Pi, a MCP9808, an old Mac Mini (early 2008), InfluxDB, Grafana, a bit of Python, and runit.
iOS Environments Variables
I find that there are usually at least two distinct environments in which any iOS project is built: generally one set of configuration for development and another for production. Each mode usually requires its own set of configuration: resource URLs for data fetching and manipulation, 3rd party service authentication keys, and the like. Usually I see these types of configurations defined through conditional macros inline with application code, like so:
An implementation of the future construct, inspired by Celluloid's block based futures, which uses process forking as a means of backgrounding work.
Another URL "shortener". Srink is a simple, but non-trivial, toy application meant to demonstrate web application construction techniques. Srink was developed using outside-in, test driven development. A demo instance of srink is deployed at http//srink.us
Jobology (Technology Mentor)
A career insights and job board for Physicians by Physicians.
- OmniAuth Doximity OAuth2
Githug is designed to give you a practical way of learning git. It has a series of levels, each requiring you to use git commands to arrive at a correct answer.