I’m a software developer with prior experience in backend and system-focused development, currently rebuilding and updating my technical profile in Canada.
In my earlier work, I focused on internal applications, system integration, and long-running software using C#, .NET, SQL Server, and Python. Due to long-term external limitations, I had limited access to modern cloud platforms. Since moving to Canada, I’m intentionally closing that gap through hands-on projects, learning-focused experimentation, and open-source work.
This GitHub profile reflects that journey — learning, refining, and building step by step.
📍 Vancouver, BC, Canada
I previously worked on internal business and operational systems where reliability, clarity, and long-term maintenance mattered more than rapid feature growth.
That experience shaped how I approach software today:
- careful changes
- understandable behavior
- respect for system boundaries
- preference for fundamentals over trends
Languages & Platforms
- C# / .NET
- Python
- Dart / Flutter
Core Interests
- Backend development fundamentals
- Networking basics
- Rule-based systems and decision logic
- Clear, explainable software design
What I’m actively improving
- Modern development workflows
- Code quality and refactoring practices
- Containerization and deployment basics
- Cloud concepts through practical projects
Educational HTTP/HTTPS proxy (Python)
SegmentedProxy is a learning-focused project designed to explore how proxies and network traffic behave in practice.
It focuses on:
- HTTP request forwarding
- HTTPS CONNECT tunneling
- Rule-based routing (direct, upstream, block)
- Traffic segmentation strategies
- Clear, documented behavior
This project is not intended for production use. Its purpose is to make networking concepts easier to understand through real, readable code.
👉 Repository: https://github.com/amirpooyan-r/segmented-proxy
I believe:
- strong fundamentals matter
- small, focused projects teach more than large abstractions
- documentation is part of code quality
- systems should be understandable, not opaque
Most of my recent work reflects this mindset.
I’m open to:
- thoughtful technical discussions
- learning from others
- code review and feedback
- collaborating on small, well-scoped projects
Thanks for visiting my GitHub profile.