Interests

What I value

Maintainability
Code should be understandable by someone else six months later, and I should be able to explain the intent when I reread it myself.
Scalability
Design so that you can tell in advance where the bottleneck will be when users and data grow.
Readability
Prioritize long-term readability and ease of change over short-term implementation speed.
Explicit Architecture
Make responsibilities, data boundaries, sync direction, and update ownership explicit — never rely on tribal knowledge.
Operational Simplicity
Anything that gets complicated in operation should be reconsidered at design time. Complexity costs more the later it surfaces.