VodovozOrganization/Vodovoz
Nov 2024 – Feb 2026
16 Months active
Languages Used
C#SQLXMLGroovycshtmlcsprojxmlRDL
Technical Skills
API DevelopmentAPI IntegrationAccess ControlBackend DevelopmentBusiness IntelligenceCode Clarity
N-Sem
PROFILE
N-sem
Semen Nikiforov developed and maintained core business and operational features for the VodovozOrganization/Vodovoz repository, focusing on backend workflows, data integrity, and reporting automation. He engineered robust API integrations and service layers using C# and SQL, modernized the codebase with architectural refactoring, and improved deployment through Docker and Jenkins-based CI/CD. His work included implementing document workflows, enhancing financial and logistics reporting, and introducing validation and error handling to ensure data quality. By driving UI/UX improvements and integrating external systems, Semen delivered scalable, maintainable solutions that improved reliability, streamlined operations, and enabled more accurate analytics for business stakeholders.
Overall Statistics
Feature vs Bugs
69%Features
Repository Contributions
833Total
Bugs
160
Commits
833
Features
357
Lines of code
81,590
Activity Months16
Your Network
11 peopleShared Repositories
11
Art8mMember
AndreyMember
David BidenkoMember
Sergey EfimovMember
Vadim GordeevMember
Vadim GordeevMember
Bidenko DavidMember
David BidenkoMember
AutomergeMember
Work History
February 2026
2 Commits • 1 Features
Feb 1, 2026February 2026 monthly summary for Vodovoz (VodovozOrganization/Vodovoz). Key focus: validation of fuel issuance and readability of financial reporting. Delivered a critical bug fix and a report enhancement, improving data integrity, compliance, and business decision support.
2 Commits • 1 Features
Feb 1, 2026February 2026 monthly summary for Vodovoz (VodovozOrganization/Vodovoz). Key focus: validation of fuel issuance and readability of financial reporting. Delivered a critical bug fix and a report enhancement, improving data integrity, compliance, and business decision support.
February 2026
January 2026
23 Commits • 9 Features
Jan 1, 2026January 2026 (VodovozOrganization/Vodovoz): Delivered targeted improvements across balance calculations, dialog access, codebase maintenance, and external integration, culminating in higher data accuracy, security, and maintainability along with enhanced user guidance and reporting. Key features delivered: - Balance calculation and calibration integration across dialogs and reports: aligned starting balances in reports, derived balances from calibration data where applicable, and supported calibration id parameter. - Dialog access control: added rights/permissions validation when opening dialogs to prevent unauthorized access. - Repository placement and file rename (refactor/maintenance): moved employee-related requests into the repository and updated file naming/structure for clarity. - Update SOAP client (CBR integration): updated SOAP client to reflect latest interface and compatibility. - Help display and reporting improvements: added help content display and updated fuel expense report for ongoing reporting improvements. Major bugs fixed: - Fixed report table and repository query issues to improve correctness and performance. - Division by zero guard in relevant calculations to prevent runtime errors. - Mileage calculation validation to avoid incorrect results. - Null checks added in report generation to prevent null reference errors. - VAT calculation corrections for invoices without shipment on prepayment or on credit. - General query reliability improvements for database interactions. Overall impact and accomplishments: - Significantly improved data quality and reliability in balances and reports, reducing error-prone manual corrections. - Strengthened security with per-dialog access checks and safer data access patterns. - Improved maintainability and scalability through repository refactor and naming updates. - Enhanced external integration stability with updated CBR SOAP client, supporting future interface changes. - Better user guidance and reporting visibility via help content and updated fuel expense reporting. Technologies/skills demonstrated: - Calibration-driven balance logic, null safety, and robust error handling. - Security-conscious design with runtime rights validation. - Codebase maintenance practices including refactoring and naming clarity. - SOAP-based integration and backward-compatibility considerations. - Data integrity, reporting reliability, and QA-focused bug fixing. Repository: VodovozOrganization/Vodovoz
January 2026
23 Commits • 9 Features
Jan 1, 2026January 2026 (VodovozOrganization/Vodovoz): Delivered targeted improvements across balance calculations, dialog access, codebase maintenance, and external integration, culminating in higher data accuracy, security, and maintainability along with enhanced user guidance and reporting. Key features delivered: - Balance calculation and calibration integration across dialogs and reports: aligned starting balances in reports, derived balances from calibration data where applicable, and supported calibration id parameter. - Dialog access control: added rights/permissions validation when opening dialogs to prevent unauthorized access. - Repository placement and file rename (refactor/maintenance): moved employee-related requests into the repository and updated file naming/structure for clarity. - Update SOAP client (CBR integration): updated SOAP client to reflect latest interface and compatibility. - Help display and reporting improvements: added help content display and updated fuel expense report for ongoing reporting improvements. Major bugs fixed: - Fixed report table and repository query issues to improve correctness and performance. - Division by zero guard in relevant calculations to prevent runtime errors. - Mileage calculation validation to avoid incorrect results. - Null checks added in report generation to prevent null reference errors. - VAT calculation corrections for invoices without shipment on prepayment or on credit. - General query reliability improvements for database interactions. Overall impact and accomplishments: - Significantly improved data quality and reliability in balances and reports, reducing error-prone manual corrections. - Strengthened security with per-dialog access checks and safer data access patterns. - Improved maintainability and scalability through repository refactor and naming updates. - Enhanced external integration stability with updated CBR SOAP client, supporting future interface changes. - Better user guidance and reporting visibility via help content and updated fuel expense reporting. Technologies/skills demonstrated: - Calibration-driven balance logic, null safety, and robust error handling. - Security-conscious design with runtime rights validation. - Codebase maintenance practices including refactoring and naming clarity. - SOAP-based integration and backward-compatibility considerations. - Data integrity, reporting reliability, and QA-focused bug fixing. Repository: VodovozOrganization/Vodovoz
December 2025
25 Commits • 9 Features
Dec 1, 2025Monthly performance summary for 2025-12: Focused on delivering automation, reliability, and deployment readiness to drive faster, safer, and scalable customer communications and operations. Delivered features and fixes with strong business impact, streamlined configuration, and robust resource management across the Vodovoz repository.
25 Commits • 9 Features
Dec 1, 2025Monthly performance summary for 2025-12: Focused on delivering automation, reliability, and deployment readiness to drive faster, safer, and scalable customer communications and operations. Delivered features and fixes with strong business impact, streamlined configuration, and robust resource management across the Vodovoz repository.
December 2025
November 2025
34 Commits • 17 Features
Nov 1, 2025November 2025 Vodovoz monthly summary focusing on architectural improvements, feature deliveries, data integrity, and operational excellence across the Vodovoz repository. The month emphasized scalable service architecture, enhanced driver/contact workflows, improved data accuracy in debt and reporting, and expanded notification/communication capabilities, while maintaining stability through code-cleanup and quality fixes.
November 2025
34 Commits • 17 Features
Nov 1, 2025November 2025 Vodovoz monthly summary focusing on architectural improvements, feature deliveries, data integrity, and operational excellence across the Vodovoz repository. The month emphasized scalable service architecture, enhanced driver/contact workflows, improved data accuracy in debt and reporting, and expanded notification/communication capabilities, while maintaining stability through code-cleanup and quality fixes.
October 2025
61 Commits • 30 Features
Oct 1, 2025За октябрь 2025 года в репозитории Vodovoz выполнена крупная архитектурная переработка ядра проекта, добавлены новые функциональные блоки и улучшено качество кода, что напрямую влияет на стабильность и скорость вывода бизнес-аналитики. Реализованы системные улучшения для расширяемости, мониторинга и интеграций, что сокращает время вывода критических функций и упрощает внедрение новых требований. Внедрены процессы и инструменты, поддерживающие устойчивый темп разработки и качество поставляемого кода.
61 Commits • 30 Features
Oct 1, 2025За октябрь 2025 года в репозитории Vodovoz выполнена крупная архитектурная переработка ядра проекта, добавлены новые функциональные блоки и улучшено качество кода, что напрямую влияет на стабильность и скорость вывода бизнес-аналитики. Реализованы системные улучшения для расширяемости, мониторинга и интеграций, что сокращает время вывода критических функций и упрощает внедрение новых требований. Внедрены процессы и инструменты, поддерживающие устойчивый темп разработки и качество поставляемого кода.
October 2025
September 2025
66 Commits • 29 Features
Sep 1, 2025September 2025 Vodovoz monthly delivery focused on delivering high-value features, stabilizing core flows, and enabling deeper analytics. The work spanned UI/UX modernization, data binding and async operations, fleet telematics enhancements, and backend efficiency improvements, driving improved usability, reliability, and actionable insights for product, sales, and operations teams.
September 2025
66 Commits • 29 Features
Sep 1, 2025September 2025 Vodovoz monthly delivery focused on delivering high-value features, stabilizing core flows, and enabling deeper analytics. The work spanned UI/UX modernization, data binding and async operations, fleet telematics enhancements, and backend efficiency improvements, driving improved usability, reliability, and actionable insights for product, sales, and operations teams.
August 2025
24 Commits • 9 Features
Aug 1, 2025August 2025 Vodovoz development summary: Key features delivered include fuel issuance specification with a new data model and rules, and extensive search/query enhancements for orders and journals. Introduced a separate Unit of Work for per-order codes to improve transactional isolation. DTOs and repositories were updated with a new property and secret identifiers, accompanied by centralized security/secrets configuration. Major reliability improvements were achieved through enhanced validation and error handling, and several bugs were fixed impacting payments, code handling, and data consistency. Overall impact: strengthened data integrity, improved financial and operational visibility, and a more maintainable, secure codebase. Technologies demonstrated: C#, Unit of Work pattern, DTOs/repositories, data validation, error handling, secret management, and database integrity via foreign keys.
24 Commits • 9 Features
Aug 1, 2025August 2025 Vodovoz development summary: Key features delivered include fuel issuance specification with a new data model and rules, and extensive search/query enhancements for orders and journals. Introduced a separate Unit of Work for per-order codes to improve transactional isolation. DTOs and repositories were updated with a new property and secret identifiers, accompanied by centralized security/secrets configuration. Major reliability improvements were achieved through enhanced validation and error handling, and several bugs were fixed impacting payments, code handling, and data consistency. Overall impact: strengthened data integrity, improved financial and operational visibility, and a more maintainable, secure codebase. Technologies demonstrated: C#, Unit of Work pattern, DTOs/repositories, data validation, error handling, secret management, and database integrity via foreign keys.
August 2025
July 2025
20 Commits • 3 Features
Jul 1, 2025July 2025 monthly summary for Vodovoz (VodovozOrganization/Vodovoz). Delivered a set of targeted reporting improvements, refreshed dependencies for better compatibility, and fixed critical issues to stabilize report generation and UX. These efforts improve decision support, reduce maintenance risk, and demonstrate strong cross-functional collaboration across frontend, SQL, and library integration.
July 2025
20 Commits • 3 Features
Jul 1, 2025July 2025 monthly summary for Vodovoz (VodovozOrganization/Vodovoz). Delivered a set of targeted reporting improvements, refreshed dependencies for better compatibility, and fixed critical issues to stabilize report generation and UX. These efforts improve decision support, reduce maintenance risk, and demonstrate strong cross-functional collaboration across frontend, SQL, and library integration.
June 2025
34 Commits • 11 Features
Jun 1, 2025June 2025 monthly summary for Vodovoz (VodovozOrganization/Vodovoz). Focused on delivering tangible business value through robust code processing workflows, API stabilization of ЧЗ, UI correctness, and automated deployment readiness. Key outcomes include improvements to the code processing workflow, API ЧЗ interface changes and error handling improvements, driver API/service refinements, UI/printing/signature fixes, and Jenkins-based CI/CD setup. These efforts increased processing reliability, reduced manual interventions, improved data integrity (including enum status and error tracking in the scanned-codes data), and enabled faster delivery of documents and updates to customers.
34 Commits • 11 Features
Jun 1, 2025June 2025 monthly summary for Vodovoz (VodovozOrganization/Vodovoz). Focused on delivering tangible business value through robust code processing workflows, API stabilization of ЧЗ, UI correctness, and automated deployment readiness. Key outcomes include improvements to the code processing workflow, API ЧЗ interface changes and error handling improvements, driver API/service refinements, UI/printing/signature fixes, and Jenkins-based CI/CD setup. These efforts increased processing reliability, reduced manual interventions, improved data integrity (including enum status and error tracking in the scanned-codes data), and enabled faster delivery of documents and updates to customers.
June 2025
May 2025
51 Commits • 30 Features
May 1, 2025Month: 2025-05 Key features delivered: - API ЧЗ: Implemented endpoints and added new client methods to enable ЧЗ integration; commits include d34e073bca9a8fabd90815cfd8730a56e30d9411 and 842d04745176b6dba19d94cb87cc670f750c3b58. - Worker-driven document workflows: Implemented sending documents from the worker; processing of document withdrawal from turnover; added support for EDO-related reporting (control by EDO) and UPD-based withdrawal reports, including an EDO control report query. - Reporting and controls: Generated/retrieved reports for EDO control and withdrawal control by UPD; added query in EDO reporting as part of control workflow. - Scanned codes data model and service: Introduced storage class for scanned codes and a dedicated service; centralized code-check logic within the ЧЗ service; updated data model and table for scanned codes. - Architecture and deployment enhancements: Created worker project scaffolding and performed architectural refactor; implemented service layer changes to support new workflows; distributed packages across multiple services/workers; enhanced logging and CI configuration (Jenkins) and introduced pre-commit checks and grouping by order to streamline batch operations. Major bugs fixed: - Fixed restrictions in the subquery of the order log; corrected document status updates in document workflow; resolved a merge-time error; fixed a client-side error; removed an unnecessary code-status check; corrected saving of codes in API driver; cleaned up configurations and addressed review feedback; resolved service dependency issues and logic gaps. Overall impact and accomplishments: - Significantly improved automation and reliability of document processing and EDI workflows, enabling faster, cleaner end-to-end processing and better compliance reporting. - Enabled modular deployment and faster rollout through worker-based architecture and package distribution across services; improved observability with enhanced logging and CI integration. - Data model improvements and centralized code validation strengthen integrity of scanned-code workflows and ЧЗ routing; reduced post-merge regressions through targeted fixes. Technologies/skills demonstrated: - API development (ЧЗ), worker architecture, service-oriented design, and data modeling for scanned codes. - Logging enhancements, CI/CD integration (Jenkins), and pre-commit quality checks. - Reporting, error handling improvements, and ML workflow alignment (ML dialogue check) as part of service layer enhancements.
May 2025
51 Commits • 30 Features
May 1, 2025Month: 2025-05 Key features delivered: - API ЧЗ: Implemented endpoints and added new client methods to enable ЧЗ integration; commits include d34e073bca9a8fabd90815cfd8730a56e30d9411 and 842d04745176b6dba19d94cb87cc670f750c3b58. - Worker-driven document workflows: Implemented sending documents from the worker; processing of document withdrawal from turnover; added support for EDO-related reporting (control by EDO) and UPD-based withdrawal reports, including an EDO control report query. - Reporting and controls: Generated/retrieved reports for EDO control and withdrawal control by UPD; added query in EDO reporting as part of control workflow. - Scanned codes data model and service: Introduced storage class for scanned codes and a dedicated service; centralized code-check logic within the ЧЗ service; updated data model and table for scanned codes. - Architecture and deployment enhancements: Created worker project scaffolding and performed architectural refactor; implemented service layer changes to support new workflows; distributed packages across multiple services/workers; enhanced logging and CI configuration (Jenkins) and introduced pre-commit checks and grouping by order to streamline batch operations. Major bugs fixed: - Fixed restrictions in the subquery of the order log; corrected document status updates in document workflow; resolved a merge-time error; fixed a client-side error; removed an unnecessary code-status check; corrected saving of codes in API driver; cleaned up configurations and addressed review feedback; resolved service dependency issues and logic gaps. Overall impact and accomplishments: - Significantly improved automation and reliability of document processing and EDI workflows, enabling faster, cleaner end-to-end processing and better compliance reporting. - Enabled modular deployment and faster rollout through worker-based architecture and package distribution across services; improved observability with enhanced logging and CI integration. - Data model improvements and centralized code validation strengthen integrity of scanned-code workflows and ЧЗ routing; reduced post-merge regressions through targeted fixes. Technologies/skills demonstrated: - API development (ЧЗ), worker architecture, service-oriented design, and data modeling for scanned codes. - Logging enhancements, CI/CD integration (Jenkins), and pre-commit quality checks. - Reporting, error handling improvements, and ML workflow alignment (ML dialogue check) as part of service layer enhancements.
April 2025
46 Commits • 15 Features
Apr 1, 2025April 2025 — Vodovoz development delivered significant features, migrations, and stability improvements across the platform. Key outcomes include enhanced observability through logging system enhancements; entity-based data modeling by creating entities from EDO containers and moving delivery charts to entities; robust API flow with core request handling, repository interactions, and PR automation; schema changes and type migrations enabling accurate data tracking and status checks; and broad bug fixes that improve data integrity, validation, and parsing. These efforts reduce risk, enable multi-organization operations, and support new integrations (e.g., SMS sending, TrueMark API) while improving reporting templates and general system reliability.
46 Commits • 15 Features
Apr 1, 2025April 2025 — Vodovoz development delivered significant features, migrations, and stability improvements across the platform. Key outcomes include enhanced observability through logging system enhancements; entity-based data modeling by creating entities from EDO containers and moving delivery charts to entities; robust API flow with core request handling, repository interactions, and PR automation; schema changes and type migrations enabling accurate data tracking and status checks; and broad bug fixes that improve data integrity, validation, and parsing. These efforts reduce risk, enable multi-organization operations, and support new integrations (e.g., SMS sending, TrueMark API) while improving reporting templates and general system reliability.
April 2025
March 2025
115 Commits • 51 Features
Mar 1, 2025Monthly summary for Vodovoz (March 2025): Focused on delivering substantial UI/data integrity improvements, scalable code management, and reliable end-to-end document workflows. Key features were delivered with user value and maintainability in mind, while a broad set of bug fixes stabilized core functionality.
March 2025
115 Commits • 51 Features
Mar 1, 2025Monthly summary for Vodovoz (March 2025): Focused on delivering substantial UI/data integrity improvements, scalable code management, and reliable end-to-end document workflows. Key features were delivered with user value and maintainability in mind, while a broad set of bug fixes stabilized core functionality.
February 2025
58 Commits • 23 Features
Feb 1, 2025February 2025: Vodovoz delivered a substantial API and platform modernization focused on core order workflows, data fidelity, and observability. Key work included API surface improvements with core order creation endpoints and namespace refactors, code and data handling enhancements (product code mapping and response data), and a centralized validation service with refined order checks. Network orders were hardened by enforcing status constraints to prevent invalid codes, while observability was improved through event emission on order completion and updated documentation blocks. The project was modernized via a new project skeleton, relocation of functionality, removal of legacy references, and updated dependencies and namespaces. Business-value features also covered GTIN listing and order properties, clipboard-ready data for online orders, and bulk item management with UI/printing improvements. Overall, these efforts reduced ordering errors, improved traceability, and established a cleaner, scalable architecture for faster feature delivery and better analytics.
58 Commits • 23 Features
Feb 1, 2025February 2025: Vodovoz delivered a substantial API and platform modernization focused on core order workflows, data fidelity, and observability. Key work included API surface improvements with core order creation endpoints and namespace refactors, code and data handling enhancements (product code mapping and response data), and a centralized validation service with refined order checks. Network orders were hardened by enforcing status constraints to prevent invalid codes, while observability was improved through event emission on order completion and updated documentation blocks. The project was modernized via a new project skeleton, relocation of functionality, removal of legacy references, and updated dependencies and namespaces. Business-value features also covered GTIN listing and order properties, clipboard-ready data for online orders, and bulk item management with UI/printing improvements. Overall, these efforts reduced ordering errors, improved traceability, and established a cleaner, scalable architecture for faster feature delivery and better analytics.
February 2025
January 2025
69 Commits • 26 Features
Jan 1, 2025Vodovoz - 2025-01 Monthly Summary: Delivered key domain, data model, UI, and reporting enhancements with a strong emphasis on business value, data integrity, and maintainability. Focus areas included fuel domain modeling and validation, pricing update improvements, product list UI upgrades, and a comprehensive uplift to reporting capabilities (templates, view-models, and export). Reliability improved through robust exception handling and repository fixes, along with documentation and code quality improvements.
January 2025
69 Commits • 26 Features
Jan 1, 2025Vodovoz - 2025-01 Monthly Summary: Delivered key domain, data model, UI, and reporting enhancements with a strong emphasis on business value, data integrity, and maintainability. Focus areas included fuel domain modeling and validation, pricing update improvements, product list UI upgrades, and a comprehensive uplift to reporting capabilities (templates, view-models, and export). Reliability improved through robust exception handling and repository fixes, along with documentation and code quality improvements.
December 2024
96 Commits • 45 Features
Dec 1, 2024December 2024 Vodovoz development monthly summary: Focused on modernization, data modeling, and improved operational workflows across warehouse and logistics. Delivered containerized deployment and automated CI/CD for the warehouse API, introduced a new database model, integrated optimization tooling (OrTools) into logistics events and warehouse processes, extended document exchange and reporting capabilities, and enhanced observability and reliability across the platform. Implemented EDO support (creation and persistence of requests), expanded reporting with a new UI view-model and base report fixes, and improved report period handling and persistence. Strengthened reliability with centralized logging, cancellation token handling, and the Unit of Work pattern in the service layer. Added RabbitMQ-based task notifications and continued data access improvements and dependency hygiene. These efforts reduced deployment risk, improved data integrity and operational efficiency, accelerated order processing, and enabled proactive decision-making through better analytics and observability.
96 Commits • 45 Features
Dec 1, 2024December 2024 Vodovoz development monthly summary: Focused on modernization, data modeling, and improved operational workflows across warehouse and logistics. Delivered containerized deployment and automated CI/CD for the warehouse API, introduced a new database model, integrated optimization tooling (OrTools) into logistics events and warehouse processes, extended document exchange and reporting capabilities, and enhanced observability and reliability across the platform. Implemented EDO support (creation and persistence of requests), expanded reporting with a new UI view-model and base report fixes, and improved report period handling and persistence. Strengthened reliability with centralized logging, cancellation token handling, and the Unit of Work pattern in the service layer. Added RabbitMQ-based task notifications and continued data access improvements and dependency hygiene. These efforts reduced deployment risk, improved data integrity and operational efficiency, accelerated order processing, and enabled proactive decision-making through better analytics and observability.
December 2024
November 2024
109 Commits • 49 Features
Nov 1, 2024Month: 2024-11 – Vodovoz project delivered a substantial set of reliability, performance, and platform-readiness improvements. Key features delivered include System Health Check for proactive health monitoring; enhanced data analytics with Grouping functionality and UI support for grouping by up to three parameters; cross-platform readiness with Linux compatibility, application/runtime identifiers, and Enum Attributes Support; comprehensive reporting enhancements including new Report class and query, plus UI for opening/moving/displaying reports and Excel export; and major UI/UX improvements plus code cleanup and performance optimizations across the journal, filters, and workflow UI. Major bugs fixed include addressing missed mapping and installation restrictions, validation of order existence and networked order status, query stability improvements, Excel formatting and reporting issues, UI cleanup fixes, and stray line-break corrections. These changes collectively improve reliability, user experience, and data-driven decision making. Technologies/skills demonstrated include .NET/C#, UI bindings, cross-platform development, data queries and projections, architecture migration, and service-layer scaffolding.
November 2024
109 Commits • 49 Features
Nov 1, 2024Month: 2024-11 – Vodovoz project delivered a substantial set of reliability, performance, and platform-readiness improvements. Key features delivered include System Health Check for proactive health monitoring; enhanced data analytics with Grouping functionality and UI support for grouping by up to three parameters; cross-platform readiness with Linux compatibility, application/runtime identifiers, and Enum Attributes Support; comprehensive reporting enhancements including new Report class and query, plus UI for opening/moving/displaying reports and Excel export; and major UI/UX improvements plus code cleanup and performance optimizations across the journal, filters, and workflow UI. Major bugs fixed include addressing missed mapping and installation restrictions, validation of order existence and networked order status, query stability improvements, Excel formatting and reporting issues, UI cleanup fixes, and stray line-break corrections. These changes collectively improve reliability, user experience, and data-driven decision making. Technologies/skills demonstrated include .NET/C#, UI bindings, cross-platform development, data queries and projections, architecture migration, and service-layer scaffolding.
Activity
Loading activity data...
Quality Metrics
Correctness85.8%
Maintainability86.0%
Architecture82.6%
Performance78.8%
AI Usage20.6%
Skills & Technologies
Programming Languages
C#DockerfileGroovyNonePowerShellRDLSQLTypeScriptXMLcs
Technical Skills
.NET .NET Core .NET Development.NET.NET CoreAPI Client DevelopmentAPI ContractsAPI DesignAPI DevelopmentAPI IntegrationAPI RefactoringAPI ServicesAPI developmentAPI integrationASP.NET
Repositories Contributed To
Overview of all repositories you've contributed to across your timeline