Add files via upload

theonlyNischal · web-flow · commit ad2a620f5381 · 2020-02-03T18:03:08.000+05:45
diff --git a/_posts/2017-4-6-My-all-time-favourite-books.md b/_posts/2017-4-6-My-all-time-favourite-books.md
@@ -0,0 +1,79 @@
+---
+title: My all time favourite books
+subtitle:
+date: 2017-4-6 8:46:32
+author: Nischal Lal Shrestha
+author_url: http://ww1.classof2020.xyz/class/nischal-shrestha/
+categories: post
+header-image: all-time-fav.png
+layout: post
+comments: true
+---
+# How I started reading books
+
+
+Most my friends wonder what I do in my 90 minutes ride to college from New Buspark. Dear friend, I read books. There have been many influential book which greatly influenced what I believe and how I behave. I tried to spend atleast 2 hour a day reading book that will improve my life in some way.
+
+When I first started my college at NCIT, I don't know what to do those 180 minute bus ride from home-college-home. It was a misery situation looking at the same driver and conductor of **Mahanagar** **Yatayat**. Then some time between december 2016, I got a burning desire to start reading book. I cannot afford buying books, So i started downloading pdf and by that point my affair with books started.
+
+# My all time Favourite books
+
+<h3 style = "color : #2cd67c">How to Win Friends and Influence People by Dale Carnegie</h3>
+<blockquote>
+
+This book is most influential book I have ever read. This book changed my personal views in many ways and has highly changed how i behave. If you ever ask me "Which book I read first?", Grab this one.
+
+</blockquote>
+
+<h3 style = "color : #2cd67c">Think and Grow Rich by Napoleon Hill</h3>
+<blockquote>
+Most famous person I found credited their success to this book. It was hard time finishing the book but it changes how I believe. At first this book seems little crazy, the author doesn't follow any science. He has got his own science but it is not a bad investment of time reading the book.
+
+</blockquote>
+
+<h3 style = "color : #2cd67c">The Power of Positive Thinking by Norman Vincent Peale </h3>
+<blockquote>
+
+This book is little bit religious but if you are trying to built a more positive attitude, this book will certainly help you.
+
+</blockquote>
+
+<h3 style = "color : #2cd67c">Code Complete by Steve McConnell- Microsoft Press</h3>
+<blockquote>
+
+Though Most examples are written in C++, This book completely changed the way How I write my code. After finishing this book I realize what is like writing and understanding good code. This book might be a hard deal for most of novice programmer but it will not be a loosing deal trying this book.
+
+</blockquote>
+
+<h3 style = "color : #2cd67c">Clean Code - By uncle BOB</h3>
+<blockquote>
+This is the best book I have ever read. This book is written by my all time favourite programmer Robert C. Martin(a.k.a Uncle BOB). If you are aspiring a career in sortware field, you would certainly read this book.
+
+</blockquote>
+
+<h3 style = "color : #2cd67c">Rich Dad, Poor Dad</h3>
+<blockquote>
+I read the translated version of this book, This book changed my view of how money works and what it means to have a job and work for someone
+else. After reading this book I clearly understood how important it is to
+create assets and to reduce your expenses.
+
+</blockquote>
+
+<h3 style = "color : #2cd67c">The Power of Habit</h3>
+<blockquote>
+I am a memeber of 5 AM club. I used to wake up 8 in the morning but after reading this book I make up my mind to wake up at 5 in the morning.
+This book will give you an idea of how to change your habit. Do you want to wake up early? Do you want to go Jym regularly. Read this book first.
+
+</blockquote>
+
+
+
+<h3> Some ongoing books</h3>
+ <li> The Pragmatic Programmer</li>
+ <li> Invent games with python</li>
+ <li> The war of Art</li>
+
+
+<blockquote style = "color : #2cd67c">
+If you ever wish to read the above book, feel free to message me or meet me by person.
+</blockquote>
diff --git a/_posts/2017-4-8-debugging-in-c.md b/_posts/2017-4-8-debugging-in-c.md
@@ -0,0 +1,102 @@
+---
+title: "Debugging in C"
+subtitle: "Keep It Simple Sir"
+date: 2017-4-6 8:51:32
+author: "Nischal Lal Shrestha"
+author_url: http://ww1.classof2020.xyz/class/nischal-shrestha/
+categories: post
+header-image: debugging-in-c.png
+layout: post
+comments: true
+---
+# Dare To Debug
+
+C programmers are great inventors of our times. However, there are is no shortage of horror stories about programs that took twenty times to **DEBUG** as they did to **WRITE**. Many a time programs had to be rewritten all over again because the bugs present in them could not be located. Bugs are C programmer's birththright. But how do we chase them away. No sure-shot way for that. I thought if I make a list of more common programming mistakes, it might be a help. They are not arranged in any particular order. But as you realize, surely a great help!
+
+
+
+[1] Omitting ampersand(**&**) before the variables using in scanf().
+For example:
+
+		int choice;
+
+		scanf("%d",choice);
+
+Here, the **&** i.e ampersand is missing.
+
+Another common mistakes with scanf() is to give blanks either just before the format string or immediately after the format string as in;
+
+		int choice;
+
+		scanf(" %d ",%choice);
+
+Note that it is not a mistake but till you are not going to understand scanf() it will trouble you. Safety is in avoiding the blanks.
+
+[2] Using the operator **=** instead of the operator **==**.
+Note that = is used for assignmet while == is used for equality. In C equal to is not equal to equal to.
+for eg;
+		int i=10;
+
+		while(i=10)
+
+		{
+			printf("got to get out");
+			i++;
+
+		}
+
+Here the while loop become an infinite loop since every time, instead of checking the value of i against 10, it assigns
+the value 10 to i. As 10 is a non zero value the will be always true.
+
+[3] Ending a loop with a semicolon.Observes the following program;
+
+	int j=1;
+	while(j<=10);
+	j++;
+
+Here, inadverently, we have fallen in an indefinite  loop. Cause is the semicolon after the while loop.
+the semicolon is treated as the null statement by the compiler as shown below
+
+	while(j<=10)
+		;
+
+This is an indefinite loop,since the null statement keeps getting executed indefinitely as j never gets the increament.
+
+[4] Using **continue** in a **switch**. It is a common error to believe that the way the keyword break is used with loops and a **switch**; similarly
+the keyword **continue** can also be used with them. Remember that continue works only with loops, never with **switch**.
+
+[5] Forgetting the bound of an array.
+Note in C we don't have bound checking so it is upto you how you deal with this.
+
+	int num[50], i;
+
+	for(i = 0; i <= 50; ++i)
+
+		num[i] = i * i;
+
+Here, in the array num, there is no such element as num[50], since array counting begins with 0 and not 1.
+Compiler would not give a warining if our program exceeds the bounds. If no taken care of, in extremes cases, the above code might even hang the computer.
+
+
+
+# Always Remember
+
+
+<blockquote>
+
+Programming is not about being clever and obscure -- it's about how clearly your program communictate it's purpose.</blockquote>
+
+<blockquote> Code conciseness is much more less important than code readability. </blockquote>
+
+
+<blockquote> Reduction in program size necessarily doesn't mean reduction in meaning for the next programmers. </blockquote>
+
+<blockquote> Any person can write the program which computer can understad, but real programmer write program which human can understand.
+
+</blockquote>
+
+# Note
+
+If you found similar contents in the book Let Us C, page 638 -644, It is a pure accident.
+
+Looking for C examples	[Visit Novice Programmers](https://www.aakrist.me)
diff --git a/_posts/2017-7-25-pomodoro-technique.md b/_posts/2017-7-25-pomodoro-technique.md
@@ -0,0 +1,47 @@
+---
+title: Pomodoro Technique
+subtitle:
+date: 2017-7-25 8:04:9
+author: Nischal Lal Shrestha
+author_url: http://ww1.classof2020.xyz/class/nischal-shrestha/
+categories: post
+header-image: pomodoro.png
+layout: post
+comments: true
+---
+
+<h4> Don't Struggle with time. </h4>
+
+For many of us, time is our arch enemy. We are always in a race against the clock to finish our jobs, to meet the deadlines. But, **Pomodoro** **Technique** teaches us to utilize the time rather than struggling with time.
+
+<h4> What is Pomodoro Technique? </h4>
+
+The Pomodoro Technique is a time management system that encourages people to work with the time they have—rather than against it.
+
+<h4> Technique Behind This </h4>
+At its core, the technique behind is quite simple. So simple that most people often dismiss this idea.
+
+
+The basic idea is that you plan out the work you’re going to do for a day.
+Then you set a timer for 25 minutes and work on the first task you’ve
+planned. You only work on a sinle task during one time and give complete attention on this single task.
+
+If you’re interrupted, there are various
+ways of handling the interruption, but generally you strive to not be inter-
+rupted at all. You never want to break focus. At the end of the 25 minutes, you set a timer for 5 minutes and take a
+break. That’s considered 1 pomodoro.
+
+After every 4 **pomodori**, you can take a longer break usually 10-15 minutes.
+
+If you finished your task early than the allocated time, then you are supposed to **overlearning**. That is, you continue to work on the
+task by making small improvements or rereading material if you’re try-
+ing to learn something. I tend to ignore this part and move on to the
+next task immediately.
+And this is all about Pomodoro Technique, quite simple yeah?
+Francesco originally used a tomato-shaped kitchen timer to time the
+pomodori (pomodoro is Italian for tomato), but there now exist plenty
+of apps for tracking and recording pomodori.
+
+Why don't you give a try?
+
+[Learn More](https://cirillocompany.de/pages/pomodoro-technique)
diff --git a/_posts/2017-7-28-how-often-should-we-commit.md b/_posts/2017-7-28-how-often-should-we-commit.md
@@ -0,0 +1,66 @@
+---
+title: How often should we Commit?
+subtitle:
+date: 2017-7-28 11:04:9
+author: Nischal Lal Shrestha
+author_url: http://ww1.classof2020.xyz/class/nischal-shrestha/
+categories: post
+header-image: how-often-commit.png
+layout: post
+comments: true
+---
+
+<h4> Commit Often, Commit Early </h4>
+
+<blockquote>
+	"Commits to your goal..No matter what!"
+</blockquote>
+
+
+Just a line of quote may lead you to think that this post is all about commits in real life, commitments to do this, to do that, to become .. whatever?
+
+Hell No!!, This post is about git commit. I repeat .. git commit.
+
+Before, I jump on to my views on git commit, First let's know what git commit is. <strong>In a layman's term, git commit is recording the changes you have made on a version of a file/s you have.</strong>
+
+---------------------------------------------------------------------------------------------------------------------------------------------------------------
+Have you ever see people rock climbing or experienced it by yourself. What we do in rock climbing ? We climb up a little distance, and then we put anchor in the rock, we again climb up a little distance then again we put anchor in the rock. By any misfortune you ever fall, the last anchor you planted in the rock secures you. You will never fall more than a few meteres. This is all with git, you code a little bit, and whenever you find a somehow stable position, you commit. By any badluck you fail here, you can always go back to the commit and you know  it is a stable position.
+
+So,
+
+<h3>Whenever</h3>
+<li>You integrate an incipient feature, COMMIT.</li>
+<li>You integrated a working method, commit.</li>
+<li>You fine-tuned a broken link, commit.</li>
+<li>You fxed a typo, commit.</li>
+<li>You fine-tuned an erroneous indentation, COMMIT.</li>
+
+<blockquote>
+	There is no wrong in commiting diminutively minuscule changes, as long as they are relevant and make sense.
+</blockquote>
+
+
+<blockquote>
+	The best answer to question "How often should you commit?" would be <strong>"More often than you are doing now"</strong>. Commit every change that you don't think breaks something, But otherwise, the smaller the changes you commit the better.
+</blockquote>
+
+
+# What if we commit infrequently?
+
+Let us consider, we have Programmer A and Programmer B.
+Programmer A commits conventionally but our Programmer B commits "Once in a Blue Moon". When programmer A find some issue, 'A' immediately fixed it, commit it.
+But, when B find some issue, he will make some changes to fine-tune the issue but he will not commit it immediately. He then does different things maybe integrating another file, abstracting the file, he may integrate incipient feature, may abstract some old feature and only then commit.
+
+Now let's revise what we have got. From 'A' we have got a clear log of what the issue was and where the changes occurred.
+But, from our wholesale trader i.e 'B', we have a sizably voluminous pile of changes, we don't know what the issue was, where the changes occurred. Genuinely, 'B' messed everything.
+So, there is no point in committing things in a wholesale.
+
+Butt,
+Note that commits are not a quantification of quality, In fact, they are not a quantification of quantity additionally. A number of commits you have made, Lines of Code ++, Lines of Code --, issue solved, ticket closed, a bug found, they are not a quantification of quality or even quantity.
+
+So,
+Commit every change that you think WORTH COMMITING.
+Commit as long as you don't get repine about doing so.
+Commit if you don't optate to get screwed up.
+
+Quick Tip: Git messages are generally written in present tense emphasizing what the commit does. For example: Fixes wrong indentation in index.html.
diff --git a/_posts/2017-8-3-do-not-be-religious-about-tech.md b/_posts/2017-8-3-do-not-be-religious-about-tech.md
@@ -0,0 +1,46 @@
+---
+title: Don't Be Religious About Technology
+subtitle:
+date: 2017-8-3
+author: Nischal Lal Shrestha
+author_url:
+categories:
+header-image: dont_rel.png
+layout: post
+comments: false
+---
+---
+<h3> Are you Religious? </h3>
+I cannot verbally express you are a religious person or not. Regardless, you are religious or not, I hope you will agree with me that most fatal, pernicious, bloody wars in history were fought over religion(to some extent).It is quite doleful that same religious notions is incrementing about technology and software development. But, a sigh of relief, **we don't kill people if they prefer Linux to windows, or iOS to Android or Java to C++ or ...** Imagine what would be **Earth**, if Android users starts killing iOS users and vice-versa and so on....
+<blockquote>
+We don't kill people if they prefer Linux to Windows, iOS to Android, ..
+</blockquote>
+
+To some extent, every people in the technical field are religious about their technology(programming language, OS, and other). **It is quite natural to believe that what we have chose is best**. Just like sports, we are so charged with passion, enthusiasm, our all opinion are conspicuously more charged. So we always believe that our choice is **greatest of great**.
+
+#
+
+But, when such religious credence leads you to believe that every 'X' is **shit** compare to your glorious 'Y' is very **disastrous**. It is so destructive to yourself if you develop this sort of thinking. If you dogmatically pretend belief that 'Y' is best, predicated on your own, individual belief or, with the people of the same kind of mentality then you are in a **path of destruction, limitation and circumscription**. I mean, Relish life, explore every technology, **taste everything**. Possibly, you may not know that you were **starving till you tasted other things**.
+-----------------
+# Holy War: Linux Vs Windows?
+
+You could find a Linux fanboy in every group. There is no problem in being a Linux Fanboy. But, some Linux fanboys are so preoccupied with their presuppositions that they hate 'X' comparing 'X' with Linux, Linux is an authoritative figure. Linux was made to rule. 
+
+They always verbalize, Linux doesn't have the virus, ransomware.Is there no ransomware on Linux? Is there no virus on Linux? I don't think you will verbalize that unless you are **living under the rock**. Have you heard about KillDisk*, BadBunny, Rexob, Hummingbad, Turla, NyaDrop, Kaiten, Hand of Larcenist, satyg, staor, Nuxbee, kagob a, kagob b, Hasher, Diesel, Coin, binom and there were many other additionally. Certainly, No technology is best. There are ups and downs in everything.
+
+
+The same thing with Windows evangelist. When Windows get assailed by some VIRUS or RANSOMWARE. They verbalize, "Windows have more users, So there is more virus assailing Windows. Who on the earth will make virus for 10 people, comparing to 1.5 billion windows users?". 
+The quandary here is, our Windows evangelist doesn't know or is pretending not to know that more than 91% of all web servers run on Linux. If someone could hack that shit, they could pull down whole world in a matter of an hour.
+
+The discussion here is not about Linux or Windows. The main point is not to **concretise our thinking** and way of visually perceiving world. If you love **X** then it necessarily doesn't mean you should hate **Y**. Everyone is in liberty to cull whatever they like. Please don't circumscribe your options. Taste everything. There is no good reason to dogmatically insist that your technology is best at an expense of ignoring all others.
+
+So, the problem is not **awareness**, it is **atitude**.
+
+We should know,
+Not all technology are best, most of technology we use are better form of **Good**. Certainly, in different circumstances, different technology might be a better choice, even best. But, it is quite idiotic to think that your **X** is always great. Can you tell me a best **text editor** or best **best browser** for all? Certainly you know what is best for yourself but for all? NO!!Can you? We are all diverse and this is what make us more powerful. We can't have same understanding on everything and we should not. Let's accept this fact.
+
+
+
+
+So be open-minded, taste everything and don't miss opportunities to explore.
+Cheers!!
