Stop looking for technical co-founders?


Startups today are synonymous to technology companies. It is generally and mostly like a technology or a technology solution that typically solves a problem due to its sheer potential of addressing challenges of individuals, organizations, ecosystems, and in short societies at large and even beyond. Therefore, most startups can be categorized as digital natives. Quite often we miss this point.

Mobility, improvement in penetration of mobile phones, high-quality internet bandwidth along with its falling cost (data services), accessibility of data services, and the favorable global demography, urbanization has added to the frenzy of the startup revolution. Humanity is more focused on solving its problem than ever before.

Technology is a means to an end. The existence of a problem, its identification, and validation are the crux of ideation rather than working backward using technology than can potentially solve a problem or rather create a problem that a particular technology can solve. The taxonomy of ideation begins with problem identification and sheer passion to solve it.

The idea of entrepreneurship and young minds embracing it quite early in age is sort of epidemic stage now. Technical skills (or even its understanding) positions you far ahead of those who don’t have it. Ability to code is sort of becoming a norm but we must not fail to understand that expert developer & entrepreneurship are 2 mutually exclusive skills. Problem-solving skills, empathy, appreciation of a problem, and a passion to solve it is a different league and probably the most important attribute which is often missed and hence startups which seemingly are promising don’t go too far. A cool looking UI/UX application doesn’t mean it can scale to touch a billion+ lives.

There are specialized technology companies that have adopted the agile methodologies to help startups to roll out minimum viable products to validate problem statements and potential solutions before founders can scale up. Failing lean and failing fast is a new normal and acceptable. Founders need to have then Genuity of problem-solving and innovative mindset to be successful. There are lots of success stories around internet billionaires cropping out of thin air like Airbnb whose founder was not a techie. Techies are not born, it’s an acquired skill, remember that it is your experience and expertise and not the coding abilities that will make you successful.

Comments

Post a Comment

Popular posts from this blog

Git Branching Strategy

Image
​ One and a half years ago, one of our clients was experiencing serious deployment problems like on lot of merge conflicts on  every merge , ​ ​ production database scripts and committed scripts are different resulting in wrong data schema, etc We analyzed and concluded that root cause of problems is poor branching strategy. The client asked us to suggest the branching strategy that will work for them. We designed and implemented the updated Git branching strategy and solved the majority of deployment issues. Following are the branching strategies for different development workflows that we implemented for the client. Strategies for CI-CD based development There will be four main branches created for each project and they are as follows, Develop QA Staging  Pre-Production Main / Production Below is the diagram that represents the strategy with the process automation and audiences, Strategy for develop branch: When a developer starts working on a feature, a feature branch will be create
Read more

DEBUGGING at D10X

Debugging is fixing bugs, i.e., errors in the code written. It is one of the tasks a developer finds themselves in for hours while working on a project. Sometimes, it seems like a breeze to fix the bug; other times, it takes a herculean effort to correct it. These bugs come in various categories: behavioral or logical, syntactical, run time, etc. One of the categories, called heisenbug, is one of the most difficult to debug. It takes hours to days to get a sense of it. During the past three years in D10X as a developer, I have faced bugs working on different projects. Therefore, I would like to share my experience in debugging bugs. Bugs are introduced in codebases because of a lack of understanding of the requirements(logic) or how tools you use function. One common ground I found post-analysis of my debugging journey is that I fixed the logic by filling gaps in knowledge.   Over the years, we have built a workflow of debugging at D10X.  Ask a teammate if it takes more than two hours
Read more