My name is Sam, and I'm a Software Developer with previous experience in IT consulting and film and media production. In a recent role, I had the opportunity to help bootstrap and architect scalable, modular UI codebases for enterprise-level fintech platforms. I'm also a Core Contributor (Software Engineer) at the open-source project, Greenstand, which is an organization using software to help mitigate climate impacts and extreme poverty across the globe.

As my background would suggest, I'm passionate about all things visual/design-related, regularly digging into UX details and searching for ways to keep code clean and maintainable. I'm naturally curious about new technology, passionate about graphic design, and plan to continue using this space to showcase what I'm learning and working on as my career progresses.

In my spare time, I'm a film and history nerd, map-lover, and—being an eastern Washington state native—a lover of trees and the outdoors. 🌲

If your organization is searching for a growth-minded developer with professional experience, I can be reached at [email protected].

Here are some of my core engineering principles that I try to keep in mind:

• Ask Why: Investigate the "why" behind a new feature or patch. What's the nature of the problem that needs to be solved for the user?
• Modularity: Keep code as reusable and scalable as possible. Find ways to reuse design/render patterns while keeping components decoupled.
• Documentation: Use and write documentation as often as possible.
• Uniformity: Read, understand, and extend established design patterns when contributing to an existing codebase. This makes future refactors simpler and keeps developers working within the same mindset.
• Refactoring: Whether replacing an entire package or a single line of code, always understand why the current solution was chosen before replacing it (Chesterton's Fence principle).
• Accessibility: Try to define a minimum a11y standard for all new features and stories and stick with it. Refactoring existing code for a11y is more expensive than integrating it from the start.