ABOUT / IDENTITY

The name is secondary.What I buildis the identity.

Mehrdad32 is my public identity in technology — the intersection of years spent writing code, building tools, documenting what I learn, breaking things, rebuilding them, and now bringing AI and system design into the same engineering discipline.

PUBLIC_HANDLE
Mehrdad32
FIELD
Software
Systems
Artificial Intelligence
PUBLIC IDENTITY

Mehrdad32

It is more than a username. It is the trail left by years of learning, shipping software, publishing knowledge and experimenting with technology.

PRIVACY BY DESIGN

Public does not mean exposed.

I prefer to be known online by what I build and what I write — not by personal information that has nothing to do with the work.

HOW I THINK

Problem first. System second. Code third.

01

I do not shrink the problem to fit the tool.

Frameworks, languages and technologies should follow the problem. Clean code cannot rescue the wrong architecture.

02

AI is not decorative functionality.

Once AI becomes part of a product, cost, security, observability, failure modes, policy and scale become engineering concerns.

03

Software has to work.

Whether it is a tiny Windows utility or a larger platform, if a real user cannot depend on it, the job is not finished.

04

Simplicity usually requires more thinking.

I like systems that feel simple on the outside because the boundaries, architecture and trade-offs were handled carefully underneath.

THE THREAD

One path. Different forms.

2012

Writing and building

Publishing technical notes, experiments and small tools — the beginning of the archive that still lives on this site.

BUILD

Real software

Windows, .NET, Android, system utilities, networking and products — moving from individual tools toward larger software systems.

SYSTEMS

Seeing the whole system

Architecture, APIs, security, data, operations, developer experience and decisions that extend far beyond a repository.

AI

AI as architecture

My current focus is where models leave the demo environment and become engineered components of real systems.

OPERATING PRINCIPLES

A few rules I tend to carry everywhere.

01
Build before bragging.
02
Understand the system, not just the syntax.
03
Automate what should not consume human attention.
04
Privacy is a feature.
05
Observability before guessing.
06
Simple does not mean naive.
07
AI needs engineering, not magic.
08
Leave things better than you found them.
THE ARCHIVE
545ARCHIVED
ARTICLES

This did not start yesterday.

A large part of this site is a real archive of years spent writing about software, Windows, programming, networking and technology. Some articles are old by design — history is useful when you can see the path that led to the present.

CONTACT

If you have something technical worth discussing, reach out.

For conversations around software, architecture, developer tooling, open source and artificial intelligence, find me through one of these channels.

No title is permanent. No stack is sacred. Keep building.