I would rather understand a system than memorise a framework.

That is roughly how I ended up writing Go after years of Python: not because it was new, but because I wanted to see the concurrency I had been abstracting away. I am most useful on the parts of a system people avoid, like the schema everyone is afraid to change, or the endpoint that got slow for reasons nobody can explain.

Outside of that: long walks with a podcast, and a running argument with myself about whether the next side project should be smaller than the last one.

Amirhosein Arabhaji is a backend software engineer based on Python/Django and Go, working on data models, query paths, cache boundaries, and access control at scale. This page exists as a dedicated, linkable identity page — see the full profile on the homepage or reach out via the contact page.