Data Mining, Web Design, Project Management, IT, and Corporate Social NetworkingWork Experience
Technology Director at Winning Our Future superPAC
December 2011 - Present (11 months)
· Technology Director for the $23 million dollar Presidental superPAC.
· Digital Master for the award winning 28 minute documentary “King of Bain:When Mitt Romney Came to Town.” (2012 AAPC Pollie Award)
Senior Technology Analyst at AutoGov Inc.
November 2010 - Present (2 years)
· Manages data protection protocols
· Completed SAS Data Mining training
· Utilizes statistical software to find data relationships
· Lead liaison with outsourced IT team
· Develop online customer service capacity and application integration
· Develop and maintain reporting and analytics for clients and software
· Maintains AutoGov website
· Coordinates technology product development
· Assist in business development proposals
· Manage various hosting solutions
President at Define Idea
June 2007 - Present (5 years 5 months)
· Project manger, designed and coder on +20 sites for small and mid-sized companies.
· Implemented Google Apps, Email and Calendar service, into new and existing businesses.
· Key role in all web asset purchases (Domains, SSL Certificates, and web services)
· Owner of an Adobe Business Catalyst distributor license.
Junior Systems Administrator at Young Williams PC
October 2009 - October 2010 (1 year 1 month)
· Responsible for end user desk-side support, helpdesk, installing operating systems, reimaging computers, patches, upgrades as well as analyzed, troubleshooted and resolved system hardware, software and networking issues.
· Managed onsite phone system (I3) for an 80 person Call Center.
· Had a role on the Helpdesk team that managed facilities remotely in four states. (+200 users)
Web Development Associate at The Learning Destination
May 2005 - October 2010 (5 years 6 months)
· Managed conversion form proprietary software to Flash.
· Developed schematic for animation of more than 150 modules.
· Conducted quality control and user acceptance testing programs.
Database Management Intern at Luhng Promotional Industries Ltd. (Hong Kong)
June 2007 - August 2007 (3 months)
· Created and managed a functional database of company assets.
· Worked with fellow employees to source promotional items in mainland China.
· Visited trade shows, in Hong Kong, to help meet company needs.
Technology Strategy Assistant at Gravitant
May 2006 - August 2006 (4 months)
· Evaluated available technology for business intelligence, and data warehousing solutions.
· Evaluated vendor proposal evaluations and reports.
· Supported Texas Health and Human Services engagements.
· Managed procurement activities for $60 million data warehouse.
University of Alabama
Bachelor of Science in Commerce & Business Administration, Operations Management, 2005 - 2009
Activities and Societies: Gamma Beta Phi Honor Society, Sigma Alpha Lambda Honor Society, Sigma Chi Fraternity, Alabama Informational Management SocietySkills & Expertise
Online Reputation Management
Categorical Data Analysis
Most “deep” apps require some amount of navigation, moving the user deeper into child views and then back out to the parent view. That navigational backtracking is typically done with a “Back” button, positioned in the top-left corner, and denoted by a pointed left side. You’ve all seen it:
The title of the entire bar is the title of this view; the Back button shows the previous, parent view’s title. Here, then, is a piece of advice for app designers: The Back button should never show the text “Back”.
This is a widespread issue, present in many extremely popular apps.
This is redundant and it provides no context. Note that Apple never does this, not in any app. Instead, they provide either the full title of the previous view, or an abbreviated/truncated version of it.
Consider the iOS Calendar app:
Apple put three legible, helpful data points into one button. This is the standard to aspire to.
If the previous view is “yours”, as in, titled and populated by you, the developer, you should always have at least a short name for it. (A related point: if you find yourself titling that view Home or Main or Start, you should rethink the app’s navigation completely.) If the view contains user-generated or otherwise unpredictable data, you should specify a reasonable maximum length for the user-generated label, truncating when necessary. As for localization, you’ve presumably already localized that previous view’s title, right?
There’s one more case where even abbreviating or truncating won’t do: a view with an unpredictable, but predictably long title. Apple was faced with this in their Music app (ex “iPod” app). Their solution was to provide a nice, big arrow glyph:
This button provides no context, but it doesn’t have to; the context is already displayed in the toolbar, right next to it. The glyph is small, easy to read, and it requires no localization. If you’re in a similar situation, use this glyph. But, don’t rush to conclude that this is the situation you’re in. Explore the above options first.
Here, then, are your options for Back-button labeling, from the most desirable to the least desirable:
A Back button labeled “Back” is never a good option.