# Code Stories: An Introduction

<span class="s"></span>

# Code Stories: An Introduction


<noscript><img alt="Image for post" class="t u v gt aj" src="https://miro.medium.com/max/3600/1*zQXjtQ-Hv-4UiQk0Sd8ykg.png" width="1800" height="600" srcSet="https://miro.medium.com/max/552/1*zQXjtQ-Hv-4UiQk0Sd8ykg.png 276w, https://miro.medium.com/max/1104/1*zQXjtQ-Hv-4UiQk0Sd8ykg.png 552w, https://miro.medium.com/max/1280/1*zQXjtQ-Hv-4UiQk0Sd8ykg.png 640w, https://miro.medium.com/max/1400/1*zQXjtQ-Hv-4UiQk0Sd8ykg.png 700w" sizes="700px"/></noscript>

Making Computer Science simple bit by bit

> If you can’t explain it simply, you don’t understand it well.

Computer Science is often seen as an esoteric discipline. Most of the learners approach it in a convoluted fashion. You hear complex mathematical jargon thrown around in corridors.
On top of that Pop culture left no stone unturned to depict Programming as a niche skill possessed by socially anxious (awkward) individuals.

However, I can’t blame them entirely. The complexity of a subject depends on a variety of things like:

*   _Are you exposed to similar branches of knowledge?_
*   _What do you want to achieve by studying it?_
*   _How much time & interest do you have?_
*   _How do you plan to approach the subject?_

Often learners skip the part where they honestly answer these questions.
This leads to all kinds of problems.
It ultimately results in their dry outlook towards a rather succulent and creative branch of knowledge.

Being a Computer Science graduate, I can assure you, things are not as difficult as they look like. Sure, they require novel thinking and good problem-solving skills. But like I said, these are skills and can be developed.

Therefore today, I am starting a series of articles that will take a programming problem and deconstruct it into intuitive puzzles.

You will see, how typical problems can be solved without any complex mumbo-jumbo if we ask ourselves the right questions and approach them systematically.

_In the coming series of essays, we will follow a consistent structure:_

*   **The Problem** ❓
*   **The Strategy** 💡
*   **The Code 🎉**

We will start with a detailed problem statement and gradually proceed towards the solution by building upon the _existing knowledge_ and _intuition_. Towards the end, we will code that solution away.

I am a big fan of **_community learning_**.When you learn together, it leads to an understanding that is beyond the realm of an isolated study session.
The best way to achieve this is to share your learnings with the community that helped you grow.

I strongly feel that these essays will rekindle your curiosity and soon you will see how fun problem solving is.

> The journey of **thousand** commits begins with a single **init** 🎊

<span class="iv ee fo iw ix iy"></span><span class="iv ee fo iw ix iy"></span><span class="iv ee fo iw ix"></span>

_Want more of this?_

_You can connect on Twitter here:_[**_abshekha_**](https://twitter.com/abshekha)
