Blog Posts

I do not consider myself an experienced speaker. I have spoken at a couple of conferences and some meetups in the past years. I have to learn lots of technical and non-technical things to become a better speaker. Still, I would like to share some resources that will help new and experienced speakers.

It all started with submitting my chatops talk to some open call for papers in April 2016. After giving the talk in CodeMotion Dubai, I felt chatops is a useful topic. Everyone working in software development can leverage it to make their life easier. My talk was a Laravel centered version of the same talk.

After almost 2 years, I gave another talk to the students of Prime College. Last time it was "Things I wished I knew while doing my tech bachelors". This time it was Career Paths for to be tech graduates. I prepared the slides at 9 and was already presenting the talk at 11:15.

I had given a talk in the PHP Developers Nepal meetup #14 in Aug 2014 about Rabbit Mq and Symfony. This time the meetup took place at Prime College today. There were 2 regular talks for this meetup and one 5 minute lightening talk about the community. For this 16th installment, we did an open discussion for the first time. The topic of open discussion was "Does automated deployment and DevOps add value to the organization?". It was the highlight of the event.

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.