RahimaSalman

I decide where the work belongs before writing it.

Before building a feature I ask whether the server should own it. Data that arrives ready needs no conversion or recalculation in the browser. The price is that the change moves onto another team's calendar, so I only push work across that line when the browser would otherwise redo it on every render.

The core path ships first, and stays simple.

Main functionality goes in first and is kept simple. Everything after that is quick to adjust — that is what simple buys you.

I don't change what I can't verify.

Under pressure I leave tightly coupled code alone rather than hand it to an AI to "optimize" — that needs proper testing. Logic changes are agreed with the manager first.