Design for change
Good architecture does not predict the future. It makes future changes cheaper.
SOFTWARE DEVELOPER · PRODUCT ENGINEER · GRAND LINE MINDSET
I’m Farshad, a developer focused on .NET, Angular and backend architecture. I like software that feels simple on the surface because the difficult decisions were made carefully underneath.
I enjoy turning messy product requirements into systems that are predictable, maintainable and actually pleasant to evolve.
Most of my work lives around backend architecture, APIs, data modeling, reliability and admin/storefront products. I tend to care about the details people only notice when they go wrong: boundaries, naming, failure states, observability, idempotency, deployment and the shape of future change.
Outside code, I’m into philosophical books, deep films, games, animation and music that changes with the moment. Some days that means minimal focus music. Some days it means something loud enough for the road.
Good architecture does not predict the future. It makes future changes cheaper.
Logs, metrics and clear states are part of the product, not an afterthought.
Abstractions are useful only when they remove more complexity than they introduce.
From technical support to production-scale backend systems — a voyage shaped by increasing ownership, architecture decisions and software that has to keep working after it ships.
Building and maintaining production backend systems across core platform services, with a focus on reliability, maintainability and shared infrastructure.
Architecture and technical decisions, developer mentoring, code reviews, production releases and hands-on development.
Scalable C#/.NET APIs, SQL Server optimization, Windows Server/IIS hosting and technical documentation.
ASP.NET MVC / C# web application development and maintenance.
CRM production bug fixes and redesign of the reporting system.
Technical support alongside Web and Windows application development.
COMMERCE · PRODUCT OWNERSHIP · END-TO-END
A production e-commerce platform designed and built as a real evolving product — from domain architecture and catalog modeling to storefront search, notifications, permissions and deployment.
BACKEND · CORE SERVICES · RELIABILITY
Backend engineering across core production services where reliability, authorization, observability and maintainability matter as much as feature delivery.
DELIVERY · OBSERVABILITY · RELIABILITY
Engineering the operational side of software — deployment, diagnostics, background processing and data systems designed to stay understandable when production gets complicated.
Tools change. The way I use them matters more — clear boundaries, explicit state, production visibility and systems that are easier to evolve than to rewrite.
Most of my day-to-day engineering lives here.
Enough frontend to own the product end-to-end.
Where reliability and operational clarity show up.
A personal music archive built around atmosphere, memory and weekly emotional arcs.
Drawn to worlds that reward attention: layered stories, strange atmospheres, philosophical questions and long-form journeys.
“The destination matters. But the crew, the scars and the voyage are what make it yours.”— a principle, not a quote
Islamic Azad University, Parand
Professional working communication and technical reading.
If you're working on a product, backend system or engineering problem that deserves careful thinking, I'd be glad to hear about it.