You can hear what a client/partner needs and you can just meet their needs. OR You can listen to them, and start building a new relationship and lay the foundation for a long-running gig. You can only succeed in that partnership when you start by focusing on solving immediate paint points but never lose track… Read More »
Alpha releases are done to test functionality for early feedback Alpha releases do not run for 6 months Alpha releases are not exposed such that consumers are able to consume and create content Telling your users, that your software is in Alpha after 5 months of launch is a lame way of telling people that… Read More »
We will see how this goes. But, for now the 5 rules for quality for me stand even today are:
– Deliver an artifact and ensure no one can find a defect;
– I can refactor the code knowing it won’t break anything;
– Code commits work like a charm and i can deliver code in environments quickly and with certainly;
– When I send this application to my dear friends in operation, they don’t hate and curse me;
– Quality meant, once my work is done it’s done
Ravi Pal aside from being a dear friend is someone I respect a lot; he is a technologist who wows me every time I talk about something. I recently came to know he has been writing a blog. I managed to read only 1 post till now and the very first post is amazing. I’d to share with… Read More »
People will soon realize that your method works (because you succeed more often) and disrupting your process makes you ineffective and no one wants to do that.
It’s interesting how when we have to select a bunch of people to be on our projects we immediately latch onto the skilled ones whether or not they are motivated and the average guys are first ones to go even if they have a vested interested in our success (as they succeed along with us).… Read More »
This article is my POV and what I want to tell the readers, and not what this reviewer thinks and what he wants to get out. This is not just an “edit” on punctuations and language but on my thoughts is my biggest deterrent on writing for any other publication and I realized that those 2 articles have been sitting in draft mode for 18 months now. It just gets “uuggghhh…”
When we see a problem on a project why don’t we take the time and fix it? Why do we get afraid of telling stakeholders that something has gone wrong and we need to course correct which might lead to an increased cost or a bit of a delay in schedule?
You can write any number of scripts (manual or automated) but unless you get yourself to be in a position where you are like a user of the site you will never know if what you are testing will meet the client’s end requirements.