This post is about my experience at NITK, what I expected it to be, what I think it should have been and what I learnt from it (too much confusion in here). If you think the title seems to be taken from somewhere, yes it has been partly stolen 😉
Life in any Indian Engineering college consists of 4 parts (the for short years), but you never know how many more you end up making from it. So lets start to explore each year a bit.
Life normally flows in this year, everything’s new and exciting. Any small event in college is like a “Mela” for the first years. Lots of advises come from drunk seniors, who learnt a lot and want you to know things beforehand; but you always get to ride the bike once. This year for me went mostly in raging and JEE preparation (please don’t do this). The raging part was awesome (no I am not lying). Raging is not good in general but to smaller extents it is a great way to know your seniors and classmates; I am still not sure if I totally oppose of it being illegal. From a programming point of view, I learned C this year (never knowing this will be kinda destiny).
This part of life- taken too carelessly, actually moulds your life. I am still confused what one should do in this phase, is it study? or aiwai-gupshup? or Hollywood? or seasons (strictly from the west)? or some kinda complex relationship ? Well I think I have had a little of all of these and I am still not content. This year is definitely a must year to do lots of stuff; be it making valuable,trustworthy friends or spend hours/days/months on your new *shiny* laptop or building your taste of music or whatever. Its never less stuff you can do. I preferred to keep study at a low priority this year and ended up screwing my GPA, I do blame that as an effect of my personal life stuff (not gonna discuss that over here). A lesson was learnt here -> never screw up your GPA, whether you learn anything or not.
Besides many find a guy/gal to keep them busy in this year, that is something I would say is worth a try too 😛
Hmm, now comes the time when you see your future head-on. Stupid stuff like placement tension, CAT/GRE preparation would come to life. Plus the problem of not getting a cool internship because of your screwed up GPA would constantly scream in your head (Little secret recipe here- try GSoC). This year I had ended up stuff that had backed me from my career path and started to focus on what to *really* learn. My GSoC came across this year’s end and was one of the most yielding experience till now. This year one should totally get into the gist of his/her subject and catch up on all that you lost enjoying for two years. Remember, a harder third year only leads to an awesome final year.
This year for me has just started and I am already writing this post too early. Not much to say, but this year is mostly about getting a “job” which I think is better the early you get. Recommendations for this year come in two ways, Enjoy! and Work Hard!. A little difficult choice to make here but I am still trying to keep my foot in both boats here.
As I have read in my Database Course that normalization is efficient and but is it really efficient?
I think I am moving rather to a no-normalization database for my GSoC project GreenSMW and why is that?
As per our needs we have to answer queries for properties or subjects and very rarely for values. So, I am considering to store the data duplicated -once with sharding (horizontal partitioning) based on properties and secondly based on subjects. I am having other considerations also and will update this post if I come up with some other idea
Yay!! I got into GSoC’12
It has been a very nice experience so far for me that I thought of writing about it. Hope it might end up somewhere in the Google results for the query “how to do a GSoC?” and help some fellow coders.
Let’s get it started!
For anything that you don’t understand please fire up Google with the to know more about the stuff. I don’t have time to point all such query results to you 😛 and you should at least know how to search the web.
What you should already know/be/have:
• You should have a good internet connection (A must as GSoC involves working on-line most of the time).
• Know some programming language(s) (even beginner level is fine). C/PHP/C++/Python/Java are common languages you can learn. But try to get deeper expertise in one.
• Get some knowledge of what Open Source Organizations are and how they work and also learn about Openhatch.org
• Have a summer (2-3 months) available for full time dedication to the job – I am sure you have this 🙂
That’s enough! Go to ‘How to start’ as soon as possible (don’t waste much time just thinking, but act)
How to start?
• Learn what is Internet Relay Chat (IRC) and how it works.
• Now that you know about IRC you can find the channel #gsoc using your favourite IRC client and talk to anyone. (This is a great place to ask but please try finding the answers yourself first)
• See the list of participating Organizations for this year (if available) and previous year, filter them by your preferred programming languages or other interests.
• Jot down few Orgs that you are interested in, go to their home page, visit their IRC channel and say ‘I would like to know about the org and volunteer’, someone will definitely turn up to help you out.
• Pick one (or more) of these Orgs you selected which interests you the most and ask them on IRC ‘Hi I am interested in your organization how do I start contributing to it?’
• Join the mailing lists of the Org and read some of the mails to get an idea of how conversation takes place. (Learn about public mailing lists too)
Good! You will now mostly tackle all difficulties yourself from here.
Important miscellaneous points:
• Don’t take Gsoc as a job rather take it as an experience where you will learn new stuff specifically: how a large org works, how they communicate, etc. I am sure you will notice GSoC brings you closer to Open Source Organizations and the idea of FOSS.
• Never ever send a mail with no subject
• Before sending a mail remember to use a spell-checker.
• Always search the internet before asking any questions on IRC or mail.