Crash Course On Operating System Blocks & Commonly Used Data Structures Overview

To be a good programmer is difficult and challenging. Writing computer programs is important and takes great intelligence and skill. Just having a good grip over your programming language doesn't necessarily make you a good programmer. If you have written enough pieces of software, necessary part of that experience is - you must learn the environment where your program will run. More you know about the system, better you are while writing your piece.

In current times, where technology keeps evolving every day both our software and hardware platforms keep changing. So, the piece of software that works fine on one platform, might have to be redesigned for another platform. This is mostly true while writing system software. But even for application software, if you understand how to modularize your software based on underlying architecture, when really to take advantage of kernel provided primitives like threading, IPC, synchronization etc., analyze benefits and trade-offs associated with them - you will feel more confident in writing your piece and the result is, a more robust and reliable software.

With this intent, this book gives you a crash course of core building blocks that make an Operating System. This book is my attempt to remove few extra pounds and just focus on core fundamentals and building blocks of Operating System and commonly used Data Structures. The intent is, more you know about how your system works, you are more likely to become a better and an effective programmer. I am confident, once you understand these building blocks; you could create your complex data structures as per your specific requirement and work on them like a charm.

INTENDED AUDIENCES
Previous familiarity with data structures and the operating system is the best combination. This book mainly has two audiences.
First category of audiences are recent grads, who have read big voluminous books but still wonder how things work. In this book, I have tried to remove possible redundancies and focus precisely on core fundamentals which I learned hard ways.

Other could be the experience professionals who want to refresh their fundamentals, especially ones coming from upper layer development, wondering how things work under the hood when they make those fancy library calls or who may want to switch to work closer to the system.