Sunday, 13 July 2014

Start small

For sometime now, I have been really drained and as unfocused as anyone can be. So many things were falling apart all around me, my 3 year relationship fell  by the way side, all my projects were half done, I was completely broke and none of my clients was responding, my pc developed a fault and nothing seem to be working. In short my life was a complete mess.

This situation made me to enter into deep reflection, soul searching and prayer. I began searching for the reason why 10+ hours can't put food on my table and why my projects take very long to complete. Why I can't seem to be able to get anywhere even after putting so much time and effort into what I do.

What I discovered 

After much soul searching, I discovered that my major problem was that I was trying to finish a whole elephant all by myself at once. That was why I couldn't finish any project that I started and often get bored with it which results in it being abandoned and left in the hall of fame for unfinished projects. 

Another pot hole to my success all this while was that I often tend to start a project from the back-end instead of the front-end. Although this  maybe argued, but as a solo developer and from the recent results of some of the changes I made. I discovered that its far more better to start a project from the front end as this will quickly help you to define and refine the domain model and the business logic, thereby giving you more bang for your efforts.

The take away

One major lesson I learned from my experience is that of "Starting Small". During the course of my inner journey and research, I discovered that as far software development  is concerned, if you are working alone or in a small team and working in a non-life threatening situation life (like commerce core system development), it is far better to start with the smallest number of features possible. Don't try to implement all the features or correct all the bugs before you set sail, rather get it into the open sea as quickly as possible and then let the early birds and beta testers lead the way. As time goes on, add features not solely based on feature request, but in line with the vision you have for the product. Peace...

No comments:

Post a Comment