Tired of ads? Enjoy an ad-free experience by signing up.
  • Insights
    This article was written by a TIA community member. Insights pieces undergo the same rigorous editorial process that newsroom-produced articles have.
Charmaine de Lazo · · 6 min read

Discuss: How important is it for non-technical founders to learn how to code?

programming-guy-red

Photo credit: Startup Stock Photos.

Discuss features short but strong and insightful opinions on interesting startup, entrepreneurship, and tech topics. Got a topic or question to suggest? Drop us an email.

If you want to build a tech startup but don’t have a programming background, should you learn how to code? Or should you hire a CTO or developer instead? Should you do both? These are common questions, and there are many opinions both from technical and non-technical perspectives.

So today, let’s hear from some non-technical founders who’ve learned how to code. They share with us their experience and how it affected the way they run their tech startups now. They have some great pieces of advice to offer too.

Editor’s note: Answers have been edited for clarity.

nitesh-agrawal

Nitesh Agrawal, co-founder at Indiez

I chose to work with a programmer because I was aware that my strength was not writing code. Rather, it was thinking ahead of the world with a vision and communicating that vision with the people working with me. And I am really good at sales and marketing. So, acquiring a new skill would have taken a lot of time, and I knew two things:

  1. Even if I learned that skill, I wouldn’t be good enough
  2. I would not want to write code in the long run

I did spend a lot of time with my co-founder to get myself acquainted with what goes into writing great-quality code. The biggest challenge was that sometimes it was difficult to communicate the product vision. I had a clear thought that a particular problem could be solved by technology, but I couldn’t propose a solution. I felt helpless a lot of times.

Sometimes it is difficult to empathize with a programmer in terms of how and why a simple thing could take so much time to accomplish. But I’ve learned to give them the ownership and make them understand the need for speed. If they understand why something is important, they would try their best and complete something ahead of time.

The most important learning I have is that you should communicate the product vision with your programmers in the most detailed way possible. Make them believe in themselves and ensure that you are on the same page with them.

Also, a lot of beauty lies in the details. Make sure that you are paying great attention to those details. Make them speak to a customer frequently so they can empathize with the problem. This will help them create a product that solves real problems!

Let’s discuss:

Stay ahead in Asia’s tech landscape

You've reached your 2 free content limit for the month. Sign up for free to read the full story.

🏄 For casual readers / 👶 Free

Basic

US$0

Free forever

Get instant access to this article and more every month

0 premium content

Unlimited news briefs

5

5 articles

Ad-free reading experience

Just US$0 per day

⌛Sign up in 20s. No payment details needed.

📖 For learners / 👍 Starter

Lite

US$4.92/month

Billed annually at US$59/year

Get instant access to this article and more every month

4

4 premium content

Unlimited news briefs & articles

Ad-free reading experience

Just US$0.17 per day

Cancel anytime

Our subscriber community includes professionals from these companies:

Stay updated on the go with our mobile app.

Get latest insights with smoother, more personalized experience through TIA mobile app.

Community Writer

Charmaine de Lazo

News editor at Tech in Asia