About
The name is a nod to the .tiff file signature. The orbit? That's how I work — creative loops, constant iteration, motion with purpose.
Who I Am
I'm Tiffany, a recent graduate and full-stack developer/designer. I graduated this spring and spent my first summer building things instead of rushing through job applications. I'm approaching the search differently — looking for teams building products that matter, not just filling open roles.
orbit.tiff started as a logo: a wordmark, a green "ready" dot, and a nebula-purple orbit looping behind it. It grew into how I approach my work — creative cycles, constant iteration, and intentional motion.
I'm a full-stack designer/developer focused on building web experiences that are intuitive, accessible, and friendly to neurodivergent minds. I love turning complex ideas into tools people actually enjoy using. I believe that thoughtful design and accessible code aren't nice-to-haves—they're foundational.
I'm based in Austin. Outside of code, you'll find me hiking, traveling, reading, and thinking about what products could make a real difference in how people work.
My Approach
Every project starts with three questions:
- What is the cognitive cost? I measure complexity not just in lines of code, but in the mental load placed on users. Simpler is almost always better.
- Who might be excluded? Accessibility isn't a feature—it's a foundation. I test with screen readers, keyboard navigation, and real users across the neurodivergent spectrum.
- Can this be more structured? Patterns, consistency, and predictability reduce uncertainty. I favor design systems over ad-hoc solutions.
Core Values
- Clarity over cleverness. Elegant solutions don't need to show off. The best interfaces feel obvious.
- Structure reduces anxiety. Predictable navigation, generous spacing, and clear visual hierarchy create safety.
- Motion should be intentional. Animation enhances meaning or it creates distraction. There is no in-between.
- Neurodiversity is design expertise. My lived experience informs every interaction pattern, every spacing decision, every word I write.
Skills & Tools
Front-End
- HTML5 & CSS3
- JavaScript (ES6+)
- PHP
- Accessibility — WCAG AA/AAA
- Responsive & Mobile-First
Design
- Figma
- Adobe Creative Suite
- Design Tokens & Systems
- Component Libraries
- Logo & Brand Identity
Back-End & Data
- Node.js / Express
- Python / Django
- MongoDB & MySQL
- RESTful APIs
- WordPress / WooCommerce
- Shopify / ECommerce
Focus Areas
- Cognitive Accessibility & UX
- AI-Assisted Development
- Educational Tools
- Design-to-Code Handoff
- Inclusive Interface Design
Designing for the Edges
Some of the best interface decisions I've made come from noticing friction that others walk right past — a layout that quietly overloads working memory, a contrast ratio that technically passes but still strains, an interaction that works fine until it suddenly doesn't.
Building for cognitive accessibility isn't a specialty I adopted — it's how I naturally see every problem. When you design for the edges first, the center takes care of itself.