Industry problem-solving experience vs. Just programming language experience

During early 2000, when I was writing code for a product from Bangalore, my company was struggling to hire. The HR team was getting feedback that one of the factors was the company was not using the latest programming languages or software stacks for development.
During those days, one sentence I heard from that company CEO sharing: Technology is to solve problems, Customer pays for solutions and not for what programming language you apply to solve, as long as you are not using 1980s programming language and/or inefficient programming language.

Fast forward to 2005s to 2012 when I was coding in London as part of my job (full time/part time), I almost didn’t see this fascination with using latest and greatest language in problem-solving. Java was equally used, like PHP, or Ruby or Python but business was making the decision based on their need vs. using the latest languages. I am not generalizing this as India vs. others. But, the truth is most Indian software programmers are fascinated using latest languages as a skill to get a high paid somewhere else (abroad/in another company), therefore that behavior is ok for IT services, but that behavior is unfavorable for product companies!

I believe once you code using one language for 1 to 2 years, you can almost code in any other programming languages for application development. Core system/kernel level product development needs years of expertise in one language though (& multiskilled in more than one).
However, coding to solve an industry problem deeper enables you to apply much deeper logic and problem-solving mindset vs. just switching to a new language because that is sexy!

The world needs deep industry problem solvers, and, Product companies take years to solve a problem at scale and go deep using languages, and some produce the extension to those languages. Basecamp doing for Ruby, Facebook for PHP and many are such examples.

Industry problem-solving at scale is first, sexy language is second.
Build an excellent solution for the customer is first, using sexy language for the solution is second.

Be Problem-solving experienced engineers any day.

assemble challenge combine creativity
Photo by Pixabay on Pexels.com

Tracking my Family Trees and fascinating history

Weekend chat with my father to hear fascinating stories from great-grandparents. We could go tracking family trees till the 1690s.

It seems his grandfather’s brother moved to Burma (Myanmar) during 1900/1910 and stayed back there. I am thinking should I try searching this branch of the family tree there.
My dad’s grandfather passed away early, and it seems his grandmother had to manage her well-being and her son’s (dad’s father = my grandfather) well being for more than 20 years. Those years were the hardest time of the family tree. And, my dad’s mom (my grandmother) played a similar role in managing the family well-being for 10 years.

My grandfather passed away early, and my father built the initial foundation for his family of 3 sisters, 2 brothers, and several nephews by taking ownership of relationship and well-being.

My father and grandfather were born in during British rule. Fascinating history on how Indian kings and British impacted tough times on villages by extracting the maximum from their farming lands.
Technically, I am the first generation in the family born in Independent India.
And, my son Sreyan is the first generation in the family born in Britain/UK, as an Indian.

The village awarded the great-grandparents & my grandfather an ‘Adhikary’ title as they were very good at managing fairness to settle disputes in the village.

I am keeping this post to a quick sharing. Hoping I am able to gather more and share more.

Big market or small market?

Fellow entrepreneur Hitesh put a tweet querying:

That got me to write this post.

Though not every problem will always be big, but if you have to choose a problem, want a bigger problem in a bigger market. There is a catch to this: The problem could be bigger, but the market is yet to become bigger. This is a classic paradox. This means the market is still not ready for the bigger problem to be solved. If the big market exists with a bigger problem, there must be a market inefficiency due to which the problem is still there.

Just an example: Corruption is a bigger problem, and there is a bigger market everywhere to solve corruption by bringing transparency, and the market inefficiency is due to physical cash which can’t be efficiently tracked and needs policy /frameworks by govt and/or institutions before you can remove inefficiencies.

Big market or small market: What do you do?

Should you enter such an inefficient market? (big market, big problem/small problem)

or

Should you instead pick a small market with a bigger problem?

The product-market fit needs a more in-depth analysis to establish size (how small market, market growth %, deeper pain/how deep, how widespread the problem) and choose a market which could be small now but might become more significant, or, select an inefficient market which could explode with billions of $ opportunities.

There is no right answer as such, it is just how you see things and which ones you want to pursue.

 

Beyond Medium, Shifting back to my own domain

Having an own active blog vs. Medium.com, I am now shifting back to use my own blog as prime blog. With the changing scenarios of Medium or any hosted solutions, which depends upon funding to survive, it is better to own a domain and a blog that is hosted and we pay it to use. They make money, in this case, WordPress makes money and I get the freedom to own my own content.

More regular blogs here.