Blog Posts

Do you write at least 10 lines of code a day in any programming language? Do you work alone or in a team? If your answer is yes to both questions, you need to learn git even if you work alone on a project. Git is the most popular version control system and it has become a must-have software engineer skill.

I have seen teams fall into this trap of git conflicts when they start using git and some type of gitflow. Merging branches to the main branch becomes a pain when there are git conflicts. In this post, I am going to reveal 3 simple rules to avoid git conflicts.

On 1-Apr-2016 For CodeMotion Dubai 2016 conference I talked about chatOps at Namshi. The main topics of the talk were:

Tests check that the code does what it is expected to do. It also gives confidence to the software engineer that the code works as intended. This equates to less or no bugs in the software. You must have heard about lots of types of automated software tests. There is unit testing, integration testing, functional testing, acceptance testing, smoke testing etc. As per Guru99's post there are more than 100 types of software testing. In this post I am going to categorize automated software tests into two, the fast ones and not fast ones.

In the past months, I was tweeting some insightful and enlightening software engineering proverbs. Like the one below

There is no pill to convert yourself as a good #programmer, it takes lots of reading, learning and practice. So start now :) #code #software

— Geshan Manandhar (@geshan) March 10, 2016

I browsed through my twitter timeline and collected them in one place.

On 7-Mar-2016 I did a short talk titled "The best CI/CD service is free (till now), lets use it" at Namshi. It was a quick rundown of Wercker CI (Continuous Integration) features and how it works.