This is actually a question that I have wrestled for months to figure out what is the intrinsic motivation that I have which keeps pushing me to build Alakazam. I am pretty certain that it’s nothing to do with immediate gains (mainly as of right now it’s not a lot). Is it the possibility of building a unicorn? I don’t think that one suite the box either. I am trying to understand what got me to work on a product in the sales and marketing space more than anything else. 2 years ago-Dulitha, would have thought that I would start a company in Developer tools or Cloud computing. But strangely enough, I somehow landed myself to build a comprehensive marketing and sales product.
One of the important things you learn when you are in the early days of building a product is that you need to understand your problem space a lot more to be able to wire a useful story. This journey of building an MVP is not discussed much because most of the time – MVPs are considered as prototypes or so called toys of the real thing. When we were building alakazam, we followed a couple of approaches in doing this. The first approach was trying to see if we could essentially write a very thin prototype that someone could easily use.
This approach yielded didn’t contribute much towards the real product we were building in term of the code. Mainly cause our repositories and code structures completely changed. On the plus side, we learned more about the possible problems that we will face in the future and how we could build the next iteration better.
Recently I have been thinking over how I learned the basics of programming. I am not blowing my horn but I am really good at what I do. I can understand technology and build architectures and write code with mastery. I wanted to find out how I can scale this out and teach more young engineers (oh the irony, when this is coming from a 23-year-old). I have been tinkering with technology for over 8 years now (from the time I was 15 years old). Maybe it’s time that made me achieve mastery. After all, Malcolm Gladwell wrote about the now infamous 10,000-hour rule.
This didn’t stop me from trying to figure out what can be used to tackle skill development. For now, I am going to think of this as a philosophy experiment. I believe there are 2 primary forms of thinking.
- Get shit done mode 💩
- What does that mean mode 🤔
To explain both these things I am going to take an example of a bricklayer laying bricks to construct a wall (After all, walls are the new hot things in town).
For the past couple of years, I have focused very deeply on managing my time. It’s understanding that time is the only thing that you cannot reverse and get back. Time must be regarded as the most precious resource of us. Few approaches I have tried included managing my time strictly with a calendar, loosely managing things with a Trello board, and then down to pen and paper.
Even though I tried to manage my time, I always failed. I failed where I underestimated the time required for a task. I didn’t anticipate other activities that will happen. I couldn’t figure out why I procrastinate on tasks.
I went back again to the white board to figure out what is the equation for this.
As an entrepreneur one thing, you’ll never get enough of is problems. They will keep on coming and there are always going to be 1000 things that are going wrong. If you have a tendency to go fix all of these 1000 things, you are going to loose. You are going to loose because you focused on battles instead of thinking about the whole war.
This brings down to the question – what problems should you focus on? I have personally found that you should work on the problems that are strategically placed to get you on the road you want to lead.
If you are working on those important problems, don’t worry too much about 1000 other things that are going wrong. You’ll eventually fix them or those problems won’t matter much.