How Curiosity Builds Great Software

I hated being with kids before I had my own. Babysitting was at the top of my list of jobs I’d never do. I just didn’t have the patience to deal with them. They require constant attention—being funny and playful. I’m the opposite. I like being in silence, talking about engineering, and engaging in deep philosophical conversations. “Marx can be fun,” no one ever said to a child.

There was this child who drove me nuts. I guess his parents gave him Red Bull for breakfast or something. It was insane being around this kid, jumping, running, breaking things apart, and constantly asking you “why”. Why are you doing that? Why does the computer make that sound? Why don’t you talk? Why are you getting angry? It was a constant battle between keeping my focus on work and having this kid asking questions. I hated every single minute of it.

A few years later, a client snapped at me: “Stop asking so many questions; you’re getting annoying.” It felt like a slap on my face. I was the annoying kid I once couldn't stand. But at that exact moment, I understood something deep: these questions weren't distractions—they were necessary. Without them, I couldn’t deeply understand my client's vision. Without them, I would just nod along like everyone else and deliver something meaningless.

Building great software is not just about following instructions—it's about relentlessly asking "why." Teams that challenge assumptions are the ones that produce truly impactful products.

Asking "why" helps teams avoid superficial solutions, focusing instead on deeper, more meaningful problems. It’s easier to stay silent, even when you hear something that doesn’t make sense. Teams that merely nod and execute instructions create mediocre products. Compliance creates comfort but kills innovation.

Steve Jobs was famously difficult—constantly questioning and relentlessly challenging his team's ideas. People often found him exhausting. Yet it was exactly this friction, this willingness to provoke and persistently question, that created breakthroughs. It forced clarity, innovation, and excellence into Apple’s products.

Many people prefer giving instructions to AI because it won’t push back—it’s comfortable. AI is exceptional at precisely executing instructions, no questions asked. But great products don't come from blind compliance. They require someone who dares to challenge your instructions, spot blind spots, and push you into uncomfortable but necessary conversations. AI can build exactly what you ask for, but it takes human curiosity and skepticism to discover what you truly need.

This is why, fundamentally, you can’t build great products with AI alone. Passionate debates, human curiosity, and skepticism remain irreplaceable in the software creation process.

This is necessary to build great software. It’s one of the secrets we learned over a decade of building digital products at Axiacore. The best software emerges from teams committed to deep questioning and healthy skepticism.

Here are three takeaways you can implement with your teams to build better products:

1. Encourage safe disagreement and reward constructive criticism.
2. Ask explicitly for alternative viewpoints and assumptions to be voiced.
3. Create a team norm around "Why?" questions to challenge decisions and explore alternatives.

Remember, if your team feels completely comfortable and friction-free, worry. Great software requires at least one annoyingly curious kid asking questions—make sure you have one of those.