Skip to main content

The disadvantage of travelling with adventurous people

This post is the result of one of my recent treks.


What do I mean by adventurous people in the title?

people who have no fear of trying out new things at a different place.

people who want to create something great out of each moment.

When you are on a trek, these are the people who are always ready to explore more.

They are always willing to try out the new food at the place.

Travelling with these kind of co-travellers sounds great, right?

But there is a downside of travelling with them.

You can not enjoy your travel with normal(read non-adventurous or 'playing-safe') people after that.


Yup, that's a disadvantage ;) .

Normal people have a fixed domain/comfort zone of their own, and it's very rare and difficult for them to come out of that. Most importantly, there are some who try to even impose this on you.

When you travel with them, you have to first provide them a well made plan for the trip. They can't come on a trip where they don't know each and every step of the trip, as they have to do a lot of planning for it. Then, you have to make sure that you can't take any route on the trip which is out of the comfort zone of any person. They can not risk themselves for your small trip.

When you suggest something new on the trip which was not planned, you are highly judged by these people. They back up their reasoning with that they are more experienced than you and you better not make decisions on your own. You should not waste their valuable time.
So, the point is, you are not

So, next time when you plan to go for some adventure with enthusiastic people, keep in mind the disadvantage of it ;)


Labels:

Comments

Post a Comment

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)
2 comments
Read more

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
Post a Comment
Read more

Android Material Showcase View - Part 1

In this series, I'll be talking about a library which is used by a lot of android developers for showcasing their in-app content,  MaterialShowcaseView . I used this library sometime back for my work and had to modify it to fit my needs. In this process, I ended up digging it a lot and would like to share what I learned. The original library offers a fix set of features, which are demonstrated by the screenshots in the README. Let's jump on the technicalities right away. The original library offers two things : 1) highlighting a view ( see the README to know what I mean by highlighting here) 2) showing a content box that tells user what the highlighted view is about. Here's how it does this : The library adds a direct view child ( this class ) in the window decor view, so that it's drawn on top of your activity's view ( here ). Then, for drawing the overlay and highlighting our view, it overrides the `onDraw()` method of this view and uses android
Post a Comment
Read more