Engineering Philosophy
I believe software zen from arises from harmony of its parts
By definition, engineering involves building a system of parts. Those parts, large and small, must fit together properly.
We have so many tools at our disposal to achieve this nirvana: Atomic databases with incremental backups, infinitely scalable compute, automatic proactive security scanning, just to name a few. Let's leverage them all in pursit of excellence for our users, success for our products, and peace of mind for ourselves.
So I Cover the Whole Stack
Working on parts of a system in isolation risks misunderstanding the system as a whole, or worse, introducing anti-patterns which weigh down the entire thing. Much like a car, each part must be considered starting from a basis of compatibility and extended to maximize the utility of each.
While there is a special place in my heart for front-end (especially mobile) and back-end (especially APIs), I'm not afraid to work on any part of the stack to get the job done.
And I Can't Ignore Details
Despite the speed of the modern software development process and increase in its complexity, attention to detail remains paramount. Balancing 80/20 does not mean sacrificing the dotting of Is and crossing of Ts.
Whether it's a foundational decision like whether or not to use a non-relational database or the subtle yet impactful need to ensure consistency in animation timing, I quite literally cannot ignore details.
Contact Me
Don't be shy now!
I'm always looking for new opportunities to grow and learn. Feel free to reach out to me via email or LinkedIn.