How I Think
Clarity beats volume. I would rather have one undeniable signal than a hundred noisy dashboards.
Restraint is strategic. What I choose not to pursue defines product quality as much as what I build.
Asset thinking is the long game. I prioritize systems that continue producing value without constant manual effort.
My Default Stack Philosophy
I optimize for reliability, maintainability, and hiring simplicity. Trendiness is not a requirement.
Most teams win faster with conventional tools and better execution discipline, not exotic architecture.
- Frontend: React + Tailwind
- Backend: Node/Express with predictable patterns
- Data: PostgreSQL as the default relational model
- Deployments: boring pipelines over clever pipelines
Rules That Save Me
If it is not in production, it is still a risk. Shipping creates real learning; planning creates assumptions.
Scope pressure is constant, so I cut aggressively before development starts.
- Cut half the scope for v1, then cut again
- Price with confidence, not fear
- Hire for specific pain, never for vague growth energy
What I Stopped Doing
I avoid recurring activities that look productive but do not compound. This includes unstructured meetings and custom work that destroys leverage.
My bias is toward systems, products, and reusable decisions.