Tushar Sadhwani
Software Engineer at Macroscope
Bengaluru, Karnataka, India
Summary
🤩
Rockstar🎓
Top SchoolTushar Sadhwani is a Python-focused software engineer with four years of experience building static analysis tooling and developer-facing features, most recently authoring and reviewing language-level checks at DeepSource and now contributing at Macroscope. He has a strong open-source footprint in well-known projects like pylint and pytest, where he fixed nuanced bugs in AST handling, typing, and assertion rewriting—work that improves tooling reliability for the wider Python community. Comfortable across back-end and testing domains, he brings practical experience spotting edge cases (e.g., numpy version crashes and docstring handling) and hardening code paths. Based in Bengaluru, he pairs formal IT training with hands-on contributions to projects that many Python developers rely on, and he’s also a speaker and technical reviewer—indicating he communicates complex ideas clearly beyond just code.
4 years of coding experience
4 years of employment as a software developer
Bachelor of Engineering - BE, Information Technology, Bachelor of Engineering - BE, Information Technology at Institute of Engineering & Technology DAVV, Indore
Github Skills (15)
linter10
unit-testing10
static-code-analysis10
refactoring10
static-analysis10
pytest10
software-quality10
unit-test10
python10
test-automation10
testing10
inference-engine9
parserator9
parser9
numpy7
Programming languages (10)
Github contributions (5)
pylint-dev/astroid
Dec 2021 - Dec 2022
A common base representation of python source code for pylint and other projects
Role in this project:
Back-end Developer
Back-end DeveloperContributions:9 reviews, 6 commits, 7 PRs in 11 months
Contributions summary:Tushar primarily contributed to the `astroid` project by fixing bugs and improving the code base. Their contributions included resolving errors related to frame calls, and correcting typing issues within the project. They also added `future=True` to frame calls for increased robustness and consistency. Furthermore, the user addressed a crash that occurred when the `numpy` library didn't have a version.
inference-enginerepresentationpythonpylintast
pylint-dev/pylint
Dec 2021 - Nov 2022
It's not just a linter that annoys you!
Role in this project:Back-end Developer
Back-end DeveloperContributions:8 commits, 8 PRs, 44 comments in 10 months
Contributions summary:Tushar primarily contributed to bug fixes and improvements within the Pylint codebase, focusing on static analysis and refactoring aspects. They addressed issues related to code comprehension, dictionary comprehensions, and conditional lambda functions within properties. Their work also involved suppressing specific pylint warnings for improved code quality analysis. This involved modifying the checker and test files.
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.