Suggestions
Bryant Baird
Software Developer | Utah React Meetup Co-Organizer
Bryant Baird is a Senior Software Engineer at TaxBit, specializing in React development.1 He has over 10 years of relevant experience in software engineering, with a strong background in front-end development.1
Bryant earned his Bachelor's degree in Computer Engineering from Brigham Young University and later completed dual Master's degrees in Business Administration and Computer Science from the University of Utah.15
Prior to joining TaxBit in July 2021, Bryant worked as a Front-End Software Engineer at Adobe for 4 years, where he contributed to the development of Adobe Analytics and Analysis Workspace.1 He also had internship experience at Qualtrics and worked as a SQL Data Analyst at Brigham Young University.1
Outside of work, Bryant is a father and describes himself as an "extrovertive introvert".2 He enjoys hiking, playing chess, and occasionally indulging in League of Legends games with his brothers.5 Bryant is also a violinist and a Mario fanatic.2
At TaxBit, Bryant contributes to the development of tax and accounting compliance solutions for the digital economy.3 He has spoken at local engineering events about handling scalability in web development4 and continues to share his expertise within the company, having provided a lunch and learn session for his team members shortly after joining TaxBit.6
Bryant is passionate about coding and enjoys making daily improvements to delight customers and enhance user experience.6 He is excited about the potential of cryptocurrency and sees his role at TaxBit as an opportunity to influence this emerging field.6
Highlights
I've been needing to get window well ladders for our newly finished basement to meet city code...
...and I came across this on the product page.
This is why UX is important. Or, at the very least, end-to-end (E2E) testing.
This matters because, had I not shopped from this vendor before, I would likely look elsewhere.
That being said, I still can't decide if I should buy. Is Not a Number (NaN) a steal?
Docs: https://lnkd.in/g3nhPztm
I had the privilege of speaking at a local engineering event this week on how developers can better handle scalability in their web applications with improved localization practices.
Thanks to UtahJS for having me, and Software Technology Group for hosting our group!
Did you know? Here's some fun insights on shorthand notation in the space. The first letter, followed by a number of letters in the middle, and the last letter. For example:
Localization: l10n Internationalization: i18n Accessibility: a11y Kubernetes: k8s
I'm sure I'm missing some?
Best, B4t
