Stock
A project that made real product development and public distribution more tangible for me; it did not remain just an exercise.
I am Seyed Erfan Hosseini Fadakari, a web developer who has spent much of his journey building, breaking, rebuilding, and constantly asking one question: why this approach?
Programming did not begin for me with memorizing syntax. What pulled me in was the ability to turn a rough idea into something that actually works—something a person can open, interact with, and get a result from.
Over time, that interest moved beyond building a page and toward understanding the whole product: where does the user enter, what should they see, where does the data come from, what happens behind the scenes, what changes when usage grows, and most importantly, is this solution actually right for the business?
I have worked across ecosystems such as Vue, Nuxt, React and Next.js on the web, with Python and Flask on the backend, while also getting hands-on with databases, caching, Docker/Podman, Nginx, Cloudflare, SEO, performance and infrastructure. Those experiences taught me something important: web development is not just writing code. It is making decisions about what should be built.
I do not believe in one stack for every project. A simple company website, an online store, an education platform and a SaaS product do not have the same problems. There is no reason to force all of them into the same architecture, framework or level of complexity.
Sometimes the best decision is a simple, affordable solution. Sometimes starting too simply means rebuilding everything a few months later. That is why I try to understand the business, users, growth path and real constraints before choosing technology.
My goal is to make design, UX, development, performance and infrastructure move in the same direction. A professional visual identity matters, but if users cannot find their way, the site is slow, its structure is weak for search, or its features do not match the real business workflow, visual polish alone does not create much value.
A project that made real product development and public distribution more tangible for me; it did not remain just an exercise.
Work on a modern web product with Next.js, including APIs, authentication, caching and client/server architecture.
From stores and service websites to specialized projects for mobile and industrial businesses, where the differences between real client needs become much clearer.
Web development is not a field where you eventually get to say “done.” Technologies change, tools improve and new problems appear. Learning is therefore part of my work, not a phase I expect to finish.
When I build something for a business, I would rather ask “what exactly are we trying to solve?” before asking “which technology should we use?”