Friday, February 20, 2015

Finally, it's Recursion.



While browsing through the internet, I came across this image, and thought it's worth a mention here! Calling the function inside it's own definition, did seem weird to me at the start. They concept seems understandable, but I would need some more practice formulating the idea into code.

As we went through some of the tracing exercises, it helped me out to analyze the working behind the code. It was exciting to break down the code and realize how it splits into smaller bunch of problems and goes on doing so until it reaches to a certain result. There were multiple examples in the lab exercise which really helped to get grasp of tracing different kids of function. After going through them, it wasn't really hard to notice that, that each function involves some-sort of a pattern and an edge case. We need to encode that pattern and merge it up with edge case to make our function properly.

It is definitely a clever idea and  I hope in the next few classes, I can more ably understand the deadly-recursion. 

Saturday, February 7, 2015

Inheritance joins my CS family


Interesting. This is what CSC148 seems after a solid base by CSC108. The course CSC148, technically, maybe just the next step, of its younger sibling, but the matter-of-fact is, it's a steep leap. A leap which provides you the perfect platform to explore, and code.

The first four weeks have gone in a jiffy, yet have been full of some-next level concrete basics for starters like us. Inheritance being the prime focus, was tackled calmly. The concept behind inheritance has been to bring the programming world as close as possible to the dimensions of the real world. It's not a concept we 'need' to understand, we have lived in a world segmented by 'Classes and its Objects', we now just extend our arms to break the bridge between an objectified world to humanly-defined objectified computer science. Sounds so complicated, but makes our lives so easy. Being humans, you can passionately code when you can analyze the real-time scenario, and understanding it by the concept of inheritance makes it lot easier and amazing.

I liked the way Prof. Heap explained us the relationships between the classes and the objects, especially via his example of the shapes. It was easy and clear-enough to get an idea of the concept. Moreover, I really liked the well-framed lab exercises as they helped practically visualize what's been taught in the class. Discussing through the tiny details and sketching down the Pseudo-code with my group members for the Assignment 1 was itself a great joy. Starting from scratch, and getting along a few hundreds of lines of code, isn't a common site for us (Times are changing). I'm looking forward, rather excited about what's to fall in our laps especially with the famous-Recursion-topic coming soon!  

Sunday, January 25, 2015

Why geeks should write?



Geeks. That’s a common term. Right? Before moving forward, I would like to share how the word ‘Geek’ came into existence. Back in 1900s, geeks were regarded as the people responsible for amusing the crowds with their bizarre, usually disgusting, acts. Now, this doesn’t seems to match much with the present context of the term geek. Today, geek is generally a very knowledgeable-even catering a certain level of obsession – about a particular interest. The era of Computer Science wasn’t an easy world to start with. The people who created the whole atmosphere of gadgets and technology didn’t have the fast processing CPUs or even a trendy iPhone.

It was sheer dedication: More failure than success, yet more satisfaction than depression. Imagine solving an integral of complicated trigonometric equation without using Wolfram Alpha, it surely sounds tedious, if not impossible. None-the-less, there was a time, when there was no Wolfram Alpha, no Google or any KhanAcademy. It was ‘Blank papers, carbon leads and genius minds’ that shaped the world we live in today.

The most obvious answer to this is that ‘writing’ is indeed the purest form of learning. That may sound awkward, but the grasping power surely enhances when you try to write down a concept rather than mentally thinking over it or maybe trying memorize a formula. It’s a mental notion that we tend to overlook the easy bits of a problem while processing it in mind, but the power of writing ensures that you give equal importance to the easy-yet-sometimes-tricky parts of a problem while framing the answer or an algorithm for it. Writing is an important factor for every person in his or her own field, but the fact that it becomes much more important among the geeks. Geeks are sharp-minded people with tons of ideas circulating among their brains, but if they aren’t able to pour those ideas properly to the other geek, or maybe even non-geek mates, they won’t be able to make the best possible contribution of their brains to bloom the humanity.

Another important consideration according to me is that, writing solutions/papers give you a better look at analyzing the writings and ideas of other counterparts. It becomes far easier to digest what the other person exactly means, improving the efficiency of the overall outcome. To exemplify this fact, I would like to mention about Linux. Linus Torvalds, the principal force behind the development of Linux kernel, was not only an exceptional hacker (geek), but it was his ability to convince his ideas on internet that helped him have almost an army of volunteers to make a platform that no one is aware of today.

If you are called Geek, it isn't just the fact that ‘You love computers, so you’re geek!’. Considering your line of interest, this gives you an unwilling power that you can channel to do something positive for the people, and writing down your views helps organize and distribute your ideas to a wider spectrum of people around the globe.