Being an Entrepreneur

Lesson 1: No matter what you do, few things will go at it's own pace ! When you can't influence them, bear them and be happy !

When I planned with other two friends of mine to leave ThoughtWorks and set up a company of our own, we had no much of idea of outside world. We were starting on getting the company name finalised, registering the company. Reading mostly on web we found out that it would take around 4 weeks to register a company. We thought we have around 4 weeks of notice period and started the procedure. Believe me if it's a government work you are bound to repeat the task at least once. It took us 8 weeks to register the company and get all the documentation done and a ton of patience, there are still couple of filing under progress which are more like nice to have.

Plus the whole government functionary is black box. So in case you are registering for a new company you would need to submit four names as a potential choice for company name. Ahhh yes 4 names, so that precisely means checking four domain name availability, all social media handles and other related stuff like github handle and all. Trust me it's easy to suggest someone a company name but when it comes to your own you would take all the time in world to finalise one. But one quick learning here is don't worry about the name much, choose what easily conveys the business and is relevant to you. There is nothing called a successful name or a unsuccessful one ! Look around yourself you have names like Google, Facebook, Twitter, Yahoo, Flipkart which are not even a dictionary word. We got to know about them when they all became famous and by the way they are all product companies. Other names are Infosys, Cognizant, TCS, HCL all big league IT Services company. So it really doesn't matter what's the company name unless you are big,  and once you are big you hardly bother about the name ! 


Popular posts from this blog

Defect Tracking System – Wastage of Money & Time ???

Image
As a QA I have been logging bugs since 5 years. But what do we do with that ? A typical flow: If this is the only thing we need to do then why taking so much of pain to have a defect tracking system . To log a standard bug (Standard Bug= Broken Functionality), we need to write steps to reproduce, pre-requisites (if any), expected result, actual result, priority, severity, snapshot (if any), Test environment details and finally save it. This takes around roughly 3-5 minutes to log a bug. To say truth, I have never seen any report coming out of defect tracking system which is of use in analyzing the pattern of bug or finding out any trend in them. All I have seen apart from tracking usage, is the summary of bugs with count based on Priority and Severity. Is that the only purpose of Defect Tracking System? If that is the case then why not use a Google spreadsheet rather then investing money of the company and time of QA in a bug logging system. I am sure if we mine the data which i
Read More »

The 3 qualities that will always help you become better at almost anything…

Image
Have we ever noticed how excited we are when we start anything? But it’s a sad fact that 70% of people abandon what they have started with so much energy and love. It could be as small as building a hobby or starting a pet project or even an activity or a side learning we started. “ Well begun is half done .” Aristotle did say this but we are judged for how we have finished something. You separate yourself fro m  the masses when you choose to give that task a finish.  The first quality is finishing off what you started and it helps develop mental stamina or willpower.   It builds confidence and inculcates as a habit in a long run. You don’t need to sign up for the mammoth activity to build this habit, even finishing mundane day-to-day routine tasks will help. Diligence — the quality of working carefully and with a lot of effort Diligence is a quality that almost never will get unnoticed. It’s one of the underlying traits of great works or success. The key to mediocrity on the o
Read More »

Test Case Paths : Happy, Sad & Bad

Image
I came back from the background of writing test cases which were categorized in either Positive or Negative test cases. Positive test cases were business flows which may or may not give any result but they will certainly not give any exception or error. Negative test cases are those test cases which were bound to result into some exception or better expressed as error causing scenarios.  Then those positive test cases were prioritized as High/Medium/Low . Finally it used to result in quite a comprehensive test case document. Then it will go through the process of review and few more updates or change of priority etc. Certainly it is a tedious process. Here in ThoughtWorks I got introduced to different way of categorizing test cases called “ Happy/Sad/Bad ”. A test case which results you in a positive result is a Happy path , for e.g. entering proper username and password on login page. A test case which yields no result like entering invalid username and invalid password on a logi
Read More »