Skip to main content

Grokking Computer Science

Computers are fun, aren't they? Today we see computers in every aspect of our lives but it is even more fun to know how computers work.

Computer Science is the study of how computers work. The study has a theoretical and mathematical focus and involves processes such as Algorithms, to solve problems.

Why should we study Computer Science?

The most important aspect of computer science is problem-solving. Problem solving is an essential skill for life. Students study the design, development and analysis of software and hardware used to solve problems in a variety of business, scientific and social contexts. Because computers solve problems to serve people, there is a significant human side to computer science as well.

There are a few reasons which explain the benefits of computer science -
  • Computing is part of everything we do.
  • It helps in solving complex and challenging problems.
  • It enables us to make positive changes in the world (to make the world a better place - a clichΓ©d line, but very true 🌝).
  • Lucrative careers πŸ’°.
  • Opportunities for true creativity and innovativeness.
  • Makes the world smaller. Democratizes the world 🌎.


I love building things and computers allow me to build things. This and the above reasons made me think about learning computer science from scratch. I learn things by doing and documenting. This enables my brain to remember stuff (at least the basic principles). In case I forget things, I can always look up the documentation πŸ’‘.

Therefore, I am starting this project today (April 11, 2019), while writing the very first post, I know this will be a long one (maybe spanning years). Since computer science is spread across various domains such as Data Structures, Algorithms, Networking, Operating Systems, Machine Learning, Data Science, Programming and many more, I am sure learning all this will take years. The human brain tends to forget stuff as time passes. This blog will serve as a sort of digital notes which I can refer to anytime (thanks to computers, again!! 🌝).


The goal is to share with the world what I have learnt and to learn what others have learnt or are learning.
One of my favourite writers is Helen Keller and she said once - 
Alone we can do so little; together we can do so much
 Thus, my belief is that collaborating with the world is the best way to learn and to grow. Hence, I welcome every suggestion by you awesome people out there to make this blog awesome like you.
We must always remember (V for Vendetta (2005))
Strength Through Unity, Unity Through Faith
Come on! let's grok computer science together ✌

Follow this post for the detailed table of contents which link through articles on different topics.


I hope you enjoyed the post. Feel free to befriend me on Facebook, Twitter or Linked In or say Hi by email.

Happy Coding 😊 and Happy Learning 😊


Popular posts from this blog

Parsing XML using Retrofit

Developing our own type-safe HTTP library to interface with a REST API can be a real pain as we have to handle many aspects - making connections caching retrying failed requests threading response parsing error handling, and more.  Retrofit, on the other hand, is a well-planned, documented and tested library that will save you a lot of precious time and headaches. In this tutorial, we are going to discuss how we can parse the XML response returned from  using the Retrofit library. To work with Retrofit, we need three classes -  Model class to map the JSON data Interfaces which defines the possible HTTP operations Retrofit.Builder class - Instance which uses the interface and the Builder API which allows defining the URL endpoint for the HTTP operation. Every method of the above interface represents on possible API call. The request type is specified by using appropriate annotations (GET, POST). The respon

Threads in Java - CountDownLatch (Part 12)

A CountDownLatch is a synchronizer which allows one thread to wait for one or more threads before starts processing. A good application of  CountDownLatch is in Java server-side applications where a thread cannot start execution before all the required services are started. Working A  CountDownLatch is initialized with a given count which is the number of threads it should wait for. This count is decremented by calling countDown() method by the threads once they are finished execution. As soon as the count reaches to zero, the waiting task starts running. Code Example Let us say we require three services, LoginService, DatabaseService and CloudService to be started and ready before the application can start handling requests. Output Cloud Service is up! Login Service is up! Database Service is up! All services are up. Now the waiting thread can start execution. Here, we can see that the main thread is waiting for all the three services to start before starting its own

Threads in Java - yield(), sleep() and join() (Part 4)

Let's say we want to stop the execution of a thread. How do we do this? There are three methods in the Thread class which can be used to stop the execution of a thread. Let us discuss these methods one by one 1. Yield method Suppose there are two threads A and B. A takes 10 minutes to complete a job while B takes only 10 seconds. At first, A and B both are in the RUNNABLE state then Thread Scheduler gives resources to A to run. Now B has to wait for 10 minutes to do a 10 seconds job. This very inefficient. Wouldn't it be great if we have some way to prevent the execution of A in between so that B can run? Fortunately, yield() method helps us in achieving this.  If a thread calls yield() method, it suggests the Thread Scheduler that it is ready to pause its execution. But it depends upon the Thread Scheduler to consider this suggestion. It can entirely ignore it. If a thread calls yield() method, the Thread Scheduler checks if there is any thread with same/high