Skip to main content

Destinations Decided.


After doing some good research, I have finalized which places I would be going to in my upcoming trip. Considering the time of the year, I have decided to start the project with the states of Himachal Pradesh and Uttarakhand. 
There are so many places in these states that I think can serve as a good destination for my trip, but I have selected three places based on some factors such as :

- good 3g connectivity
 A good internet connection is the topmost requirement.

- how scenic the place is. 
That's the reason after all why I want to travel while working.

- places that are already a travel destination for a large number of foreign tourists.
so that I can meet other people who are already doing this and interact with them.

So let's start with the names of the places:

Dharamshala:

 

 

I have heard so much about this place in past few years. 
There is a very popular suburb in Dharamshala named Mcleodganj. The headquarter of Tibetan Government-In-Exile, the place is known for a large number of Tibetans living in it and is sometimes called 'Little Lhasa'. It provides you an insight into the Tibetan culture and is very popular for the Tibetan monasteries there.
While going through online forums, I discovered that Dharamshala/Mcleaodganj is a quite popular destination among people to visit for some days while carrying their work with them. The place offers a good 3g connectivity for many providers, some cheap places to stay and the delicious Tibetan cuisine. From what I learned, this place has the resources for pursuing digital nomadism from there, but these resources are not documented anywhere and that's the reason not much people know about this.
And, there is one more reason I want to visit this place : the delicious momos.



Manali :

 

One of the most scenic hill stations in India, the place is located in the kullu valley in Himachal. 
The reason of choosing this place is that I wanted a bit developed place in Himachal, so that it can offer an opportunity for some good co-working spaces.
It's not a much popular destination among digital nomads and is still considered a place to spend summer vacations, but I think it has the potential of becoming the one and can offer everything that one would need to work from there.
There are a number of excellent cafes, cheap places to stay and a very good 3g coverage (and some public internet cafes too). For all these reasons, I think exploring this destination would prove to be quite useful in future.

Rishikesh :

 

 

Known as 'The world capital of yoga', Rishikesh is located in Uttarakhand state of India.
It is regarded as one of the holiest places to Hindus and is very popular for its Ganga Aarti that happens every evening on the banks of Ganga.
I chose this place because it's already a very popular destination among the foreigners and there is a very high chance that I might spot a good number of people with their laptops.

So, the reason for choosing this destination is I want to meet all those people and talk with them about their experience. That would help me a lot to document about the resources there and to know what the people feel about that place. 

I'll share other details about the plan (such as my travel schedule) in my next post.

Cheers !

Comments

Popular posts from this blog

Android : AbsSavedState cannot be cast to $SavedState

Android AbsSavedState cannot be cast to <View>$SavedState I came across a strange crash today. This is the stacktrace : Fatal Exception: java.lang.ClassCastException: android.view.AbsSavedState$1 cannot be cast to android.widget.ScrollView$SavedState at android.widget.ScrollView.onRestoreInstanceState(ScrollView.java:1810) at android.view.View.dispatchRestoreInstanceState(View.java:14768) at android.view.ViewGroup.dispatchRestoreInstanceState(ViewGroup.java:3123) at android.view.View.restoreHierarchyState(View.java:14746) at android.support.v4.app.Fragment.restoreViewState(SourceFile:470) at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1326) at android.support.v4.app.FragmentManagerImpl.moveFragmentsToInvisible(SourceFile:2323) at android.support.v4.app.FragmentManagerImpl.executeOpsTogether(SourceFile:2136) at android.support.v4.app.FragmentManagerImpl.optimizeAndExecuteOps(SourceFile:2092)

Android Tip : Handling back button in Fragments

Android Tip : Handling hardware back button in Fragment and DialogFragment This post explains how to handle hardware back button in a Fragment OR DialogFragment . In DialogFragment, it’s quiet straight forward to achieve this. You’ve to get the dialog instance and set onKeyListener on it : if (getDialog() != null ) { getDialog().setOnKeyListener( new DialogInterface.OnKeyListener() { @Override public boolean onKey (DialogInterface dialog, int keyCode, KeyEvent event) { if (event.getAction() == KeyEvent.ACTION_UP && keyCode == KeyEvent.KEYCODE_BACK) { Timber.i( "hardware back button pressed" ); } } }); } This can be done in the onViewCreated callback. For fragments, this method doesn’t work and fragments doesn’t have a direct callback to catch this event. So in this case, the approach that we follow is : You

DialogFragment : NullPointerException (support library)

Another weird crash this time ! Here’s the stack trace : Fatal Exception: java.lang.RuntimeException: Unable to start activity ComponentInfo{<activity.fully.qualified.path>}: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.app.Dialog.setContentView(android.view.View)' on a null object reference at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2659) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2724) at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:4524) at android.app.ActivityThread.-wrap19(ActivityThread.java) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1479) at android.os.Handler.dispatchMessage(Handler.java:102) at android.os.Looper.loop(Looper.java:154) at android.app.ActivityThread.main(ActivityThread.java:6123) at java.lang.reflect.Method.invoke(Method.java) at com.android