Bryce Guinta
Freelance Software Engineer at Freelancer
Colorado Springs, Colorado, United States
Summary
🤩
Rockstar🎓
Top SchoolBryce Guinta is a freelance software engineer based in Colorado Springs with 14 years of experience building automation, data analytics, and Linux-focused tooling. He has hands-on experience automating SSD performance testing with power and IO workloads at Seagate and contributed to robotics software at Bossa Nova, now applying that systems-level perspective to remote contract work. An active open-source contributor to the pylint ecosystem, Bryce has implemented AST transforms and fixed static-analysis edge cases in astroid while improving docs and test coverage for pylint itself. He combines low-level automation expertise with a knack for reducing false positives in developer tooling, making complex systems more reliable and easier to maintain.
13 years of coding experience
4 years of employment as a software developer
Computer Science, Computer Science at University of Colorado Colorado Springs
English
Stackoverflow
3,562reputation
1.9mreached
46answers
7questions
bokeh
top-5%
makefile
top-5%
python
top-5%
Github Skills (25)
unit-testing10
static-code-analysis10
static-analysis10
pytest10
python10
testing10
inference-engine10
software-quality10
pep10
code-analysis10
linter10
unit-test10
documentation10
bokeh9
parserator9
Programming languages (14)
Github contributions (5)
pylint-dev/astroid
Oct 2017 - Jun 2020
A common base representation of python source code for pylint and other projects
Role in this project:
Back-end Developer
Back-end DeveloperContributions:82 commits, 91 PRs, 43 pushes in 2 years 8 months
Contributions summary:Bryce primarily contributed to the `astroid` project by implementing features and fixing bugs related to the `attrs` library integration, addressing false positives in static analysis. They added a transform to handle `attr` library decorators within the astroid system, rewriting class attributes. Additionally, the user fixed bad whitespace and addressed an issue related to submodule imports in the six.moves module to improve import handling. They also resolved inference issues and added tests to ensure code quality and maintainability.
inference-enginerepresentationpythonpylintast
pylint-dev/pylint
Oct 2017 - Oct 2020
It's not just a linter that annoys you!
Role in this project:Technical Writer & QA Engineer
Technical Writer & QA EngineerContributions:55 commits, 57 PRs, 26 pushes in 3 years
Contributions summary:Bryce primarily contributed to improving the project's documentation by adding explanations for core concepts like plugins, transforms, and class descriptors. They also addressed documentation inconsistencies and improved the format. Additionally, the user fixed bugs in tests related to configuration file handling and handling of code formatting errors. They made code improvements by expanding test coverage and test infrastructure.
linterlintpep8static-code-analysiscode-quality
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.