Loading
Back to BlogProduct

Why Data Should Drive Every Technical Decision You Make

5 min read

The Expensive Lesson

Three years ago, I rebuilt an entire checkout flow for Qeenan Pedia because I was convinced the UI was the problem. We spent six weeks on a redesign. Conversion barely moved. When I finally looked at the data, the real issue was a PostgreSQL query that took 3.2 seconds on the payment confirmation endpoint. A single index fix improved conversion by 18%.

The most dangerous phrase in engineering is "I think the problem is..." without data to back it up.

Building a Data-First Culture

At every company I have led, I push for the same baseline: instrument everything before you optimize anything. That means structured logging, request tracing with OpenTelemetry, and dashboards that the whole team actually reads. Not vanity metrics - actionable ones like p95 latency, error rates by endpoint, and user funnel drop-off points.

Technology Selection by Numbers

When we chose Go over Node.js for the Karcis ID backend, it was not because Go was trendy. Load testing showed our Node services hit memory ceilings at 8K concurrent connections. Go handled 50K with half the resources. The data made the decision obvious.

  • Profile your actual workload before picking a stack
  • Benchmark with production-like data, not toy datasets
  • Measure developer velocity too - raw performance means nothing if your team ships slower

Prioritization That Actually Works

I rank every technical initiative by measured user impact. At Diro App, our analytics showed 60% of support tickets came from a single broken notification flow. Fixing that one issue freed up engineering bandwidth equivalent to hiring another developer. Data told us exactly where to spend our time.

The Mindset Shift

This is not about being anti-intuition. Experience matters. But when you pair experience with real metrics, you stop building features nobody asked for and start solving problems that actually move the needle. Every sprint, I ask the same question: what does the data say our users need most right now?

Have a project in mind?

Tell me what you want to build. I reply within one working day.