Danial Rashidi
Computer Engineering student and software & product builder.
I build practical software — web products, AI-assisted systems and automations — from vague idea to working implementation. I am interested in software, AI, products and entrepreneurship, and in turning ambiguity into something a person can actually use.
Background
I am from Iran and study Computer Engineering. The path into product and software building was not a title change — it was a gradual move from writing code to owning the problem itself: what is being built, for whom, with what trade-offs, and how it stays maintainable.
I work across software products, web, AI-assisted software development, automation and practical product engineering. Most of the work I value lives at the intersection of engineering discipline and product judgment — not demo depth, but systems that survive real use.
The interest in AI, products and entrepreneurship is connected: each is leverage for the other. I explore practical automation and agent-assisted workflows specifically where they reduce repetitive work or clarify a business path, not as a style.
How I work
I prefer calm, precise systems over noisy ones. A product is valuable when it becomes usable — the earlier it is runnable, the earlier it can be tested against reality. That means small releases, honest unknowns, and explicit responsibility for verification.
AI is part of the workflow — implementation, research, debugging, repetitive tasks and iteration go faster with it. But requirements, architecture, verification, testing and the final decision stay human. AI coding tools are leverage that must not replace verification or judgment. Nothing is presented as reviewed because a model approved it.
- 01Solve the actual problem — avoid complexity that does not improve the outcome.
- 02Ship working systems — ideas become valuable when they become usable.
- 03Use AI as leverage — faster implementation should not mean weaker verification.
- 04Keep systems understandable — readable, testable systems are easier to maintain and improve.
Direction
The current direction is specific: become a stronger product engineer, build useful software, improve engineering foundations, and build Noveno incrementally. Not a broad aspiration list — a few things done well and repeatedly, with evidence.
The longer aim is practical: more working products, better foundations in TypeScript, backend and product engineering, and systems that stay honest under real constraints — mobile, unstable network, limited tools.
Beyond software
Outside work I stay active — bodybuilding, the mountains, camping — and care about travel, music and exploring how technology and the near future evolve. Those interests keep the work grounded: life outside the editor is not separate from judgment inside it.