And the journey continues.................

Whenever you change a place, a lot of stuff changes..........here comes the most significant role of life "Adaptability....", yes the meaning of this word changes per capita. Someone calls it compromise, someone calls it flexibility, but I refer it as "adaptability".

What is your definition for it?

I define it as extension of your comfort/discomfort zone beyond your familiarity. The best way to understand it is the change in the food and communicational aspects.

I am proceeding along with my journey:

I belong to eastern part of India; yes the fluent and the legacy speaker of Hindi. I started my away home stay from the western part of India. Though the language and food habits did not change a lot but culture and climate changed (this time unbearable hot). I was pushed to a bit away from my comfort zone I was having with since my birth. 

Then, came the northern part of India; undoubtedly cooler than ever before. Again the adaptability was challenged and the comfort zone was twisted a bit more but yes, it brought up a bit more social familiarity. 

Finally, came the acid change of my life, when I shifted to Bangalore, the Silicon Valley of India. Here came the big challenge of survival in terms of food and communication, termed as the mandate of survival. Adaptability was drastically twisted and for some unexpectedly long time it was changed to compromise. Head became tail and tail became head. But it coined a new turnaround of my life, we call as "in-dependency", yes I am referring to economical in-dependency, the ultimate maturity. In-dependency, uffff....... came at the cost of compromise.  But slowly when the realization of in-dependency began to visualize.....compromise became adaptability. 

And the journey continues.................

Test vs Validation………..

As a software developer, I belong to the world of micro and nano reactions and observations, as we (Software engineers) create to and fro reactions (definitely by this I mean software functionality, i.e. users' request and applications' response).

During my development career, every day before I go through the words "test" and "validate"  once ready with deliverables. 

What are these actually? Simply literary words or do they carry weight?

My answers: yes, they do.

Description:

Whenever I create or make changes pertaining to application, I do a cat eye observation of it. I am saying like this because by that time, I know I am the expert who knows the application’s behavior and flow. It may be code wise or UI wise but yes, I know. That's why, what I do, I term it as "validation". 

But when it comes to normal user, they don't care how it should happen? They wary of how is it behaving? They don't bother about what's the flow; they worry about is it good? Is it comfortable? Is it posing any threat to my information? For the sake of these doubts, they do a round-around of the application. In my opinion, what they do is what we call "testing". They test the application, they test their comfort with the application, and they test their doubts and try to clarify them.