About

From Frontend to Systems

AMARIN is a living laboratory where product architecture, systems thinking and experimental building converge.

Origin

I started as a frontend engineer building interfaces.

Then I built startups. Then products. Then the systems behind those products.

Somewhere in between, I realized the real work is not features — it is architecture.

What This Lab Explores

→Product architecture

→Systems thinking

→Scalable MVP design

→Technical decision models

→Business–product alignment

→Growth as a system, not a tactic

Why AMARIN Exists

Because most MVPs die not from lack of code — but lack of architecture.

Because speed without systems creates technical debt, not products.

Because growth collapses when structure was never designed.

AMARIN exists to document how to build things that can actually survive success.

Beyond Software

Also, my electronics engeneering background remains present in my leisure time by implementing and building physical electronic systems, from DIY instrumentation to high-voltage probes, ignition circuits and hardware prototypes.

And after many years at the trenches is funny to realized how working with physical constraints, electricity, tolerances and real-world failure modes makes one thing very clear:

The same architectural laws govern both software and hardware systems.

Feedback loops, load, scaling, redundancy, bottlenecks, entropy, decay — systems behave the same, regardless of their medium.

AMARIN is not about code.
It is about understanding systems and designing them to survive reality.

Core Ideas

Systems Thinking— Products are organisms, not features

First Principles— Architecture before imitation

Scalable MVP— Fast but structurally sound

Intentional Engineering— Every line has a reason

Growth Systems— Metrics are architecture

AMARIN is a place to study how products are actually designed — before they become fragile companies.