Tony Trinh is a seasoned systems administrator and software engineer with 14 years of experience building reliable infrastructure and back-end systems across defense, government, and higher education environments. Based in Washington, D.C., he currently manages systems at George Mason University after roles at Peraton, Northrop Grumman, and CACI where he bridged software engineering and systems operations. An active open-source contributor, Tony has improved logging frameworks like logback and logback-android—focusing on test reliability, thread safety, and practical enhancements such as shutdown hooks and locale defaults. He also contributed to Polymer tools, adding HTTP/2 support and modernizing code with async/await, demonstrating comfort across full-stack and tooling work. Known for pragmatic problem-solving, Tony combines QA-minded rigor with systems thinking to deliver predictable, maintainable services. Colleagues would notice his attention to CI stability and a knack for turning flaky tests into dependable automation.
📄The reliable, generic, fast and flexible logging framework for Android
Role in this project:
Back-end Developer
Contributions:31 releases, 53 reviews, 1244 commits in 11 years 8 months
Contributions summary:Tony's contributions primarily involve modifications to the core and classic modules, addressing both bug fixes and functional enhancements within the logback-android project. This includes refactoring and adding logic to enable or disable features, such as enabling and disabling the stacktrace packaging data, setting a default local locale, and adding a shutdown hook. The user's commits also highlight work on improving the integration of logging event processing within the application.
The reliable, generic, fast and flexible logging framework for Java.
Role in this project:
QA Engineer / Test Automation Engineer
Contributions:159 commits, 23 PRs, 25 pushes in 2 years
Contributions summary:Tony primarily focused on improving the quality and reliability of the logback framework through test case modifications and additions. Their contributions involved fixing unit tests related to exception handling, thread safety, and configuration, particularly those failing on continuous integration systems like Cloudbees Jenkins. The user also addressed issues in documentation and release notes and made improvements to the test suite to ensure consistent results and test coverage.
loggerlogginggenericlogging-frameworkreliable
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.