Answering by questioning.

Often times I will be fighting with the problem I created out of the solution for a given problem. I have a solution which appears to works but it isn’t complete. This solution arise based on the familiarity of the problem I have in mind. That’s the wrong way, I need to describe the problem and work out on the solution on top of existing efforts.

One can relate this, when they find a solution on StackOverflow for a problem which has some familiarity with their problem. The solution might be superset or subset for your problem. But it’s a mistake to not get the real problem first. How do we do that? Often times the solution appears out of nowhere on reading documentation when I describe the problem in words to my peers or StackOverflow. Not just because of thinking out loud solves the problem but I understood the problem before describing it.

Solution isn’t fixing the existing solution but re-describing the problem.

If you don’t step forward you will always be at same place.

Everyone got questions, doubts. It’s important to feed them. Sometimes internet isn’t enough, sometimes you need to discuss the approach, show how you did it or internet is just broken. One common way is to ask personally for help or guidance. But sometimes it’s shyness, sometimes it’s ego, sometimes it’s the feeling of asking for a favor. It’s important not to spoon-feed yourself at the same time.

Also don’t be afraid to be wrong, do correct yourself.

You have to make efforts to get to the answers yourself, others’ help/guidance will just be a catalyst. It’s you who have to complete the “reaction”. Also don’t turn anyone away if they ask you for the same, afterall it’s just a cycle to be completed.


#Why ETA?

It’s important to have ETA, not just because someone else wants to coordinate with you. But it’s important for self introspection, self assessing, it’s important for one to know what all are the puzzle blocks in the problem. I remember a quote

A problem well put is half solved.

So ETA is thinking about the problem. ETA is not to impress anyone with your skills especially in software development, otherwise you would be fighting the bugs rest of the time. Some times there is pressure of determining the correct ETA, don’t give ETA for whole problem, break the into chunks and give ETA for individual chunks.

Think ETA as assembling the Rubik’s cube. It may seem messy initially, but step by step it will be solved. Solve the first layer, then second layer and lastly the third layer.

Also ETA is no excuse to comprise on quality, a half baked product to match ETA is no worth.

*ETA = Estimated time of arrival

Don’t bank on motivation. It’s inherently a bad idea.

Looking for motivation is similar to addiction IMHO. You won’t get started till you get that hit. Motivation is like a resistant virus, the same motivation won’t work every day. You will need something new each day. A particular thing about motivation is -

You will get motivation when you least expect it.

You ask, what’s the alternative. I say “Discipline”.

Discipline keeps you on target without getting deviated. Discipline tells you to “Just Do It” every single time, anywhere, anytime. Discipline is reliable, discipline is the “Motivation”. Not just discipline, self-discipline. Your mentor won’t be with you all the time, you need to train your mind to discipline itself.

Till next time.

First blog of the year

It’s just unbelievable, I didn’t wrote a blog in such a long time. Focus isn’t on blogging but not to stagnate.

There must be something happening, must be learning new technology? must be creating some app or service through code? Well that definitely was happening, I didn’t shared it. Next blog I will be describing all the good and cool stuff I have been working on. I am hopping to write a blog fortnightly for sure.

Intentionally wanted this to be short blog, just to make a promise to write more.