Skip to main content

Similarities between trying for google summer of code and hitting on a girl

I think these two are quite similar.

> The girl you are hitting on is like your gsoc mentor.

> And the relationship that you are proposing to her is like your project.

Now you all will agree with the following points:

You have to work very hard trying to convince the mentor, that you are the right person for this job and will successfully complete the project.

There are different types of mentors. Some are impressed when you immediately start contributing to the project ;), whereas others want a detailed timeline from you of how you would be doing the project.

Nobody has ever been able to understand the ideology of mentors. You think they are supporting you in the start, but they are doing the same for every other candidate.

Sometimes, there are other fellow-mentors also (girl's friends). In that case, you have to impress them also with your work.

There may be other candidates that are trying to achieve the same project. They often try to convince the mentor that they are more skilled than you but in most of the cases, what matters here is being consistant.

It totally depends on you how you choose to show your past projects to the mentor. It may directly get you the project OR your failure in your past projects, if known by the current mentor may harm your chances.

There are cases when mentor keeps responding positively to you but when the results are announced, the project is given to a person who was totally stranger before.

It's wise to start with a mentor which has recently opened projects for students and therefore is not known to many people.

On the other hand, the mentor which has been offereing projects for some years now is always crowded with candidates.

I think these points surely show some relation between the two scenarios. And there are definitely more to add, but I'll leave it to you.

Cheers !

Comments

Popular posts from this blog

Android : AbsSavedState cannot be cast to $SavedState

Android AbsSavedState cannot be cast to $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) at androi...

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...

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...