Software development is not just punching some code on the keyboard for desired output. The business side of software development always takes priority than the technicalities of it.

I have seen some software development teams are slow because they have a lot of technical debt. Some teams are naive, the members don't want to explore new things . They are stuck with 5 year old technology like FTP, old legacy framework etc. In this post, I will shed some light on the four basic and important pillars of a solid software application that support creating reliable software. This contents of post is language and framework agnostic. It is applicable to any software project.

The process of getting a completed feature or bug fix code from the development environment to your web servers is web software deployment. We have been deploying code in various ways, a decade back we were used to uploading our files using File Transfer Protocol (FTP). I would not considering copying files from the development machine to a web server a form of automated deployment, basically it was a necessary evil at that time.

If you still use FTP at this time like 22% of Nepali developers you really need to move on. In this post I will briefly mention some deployment tools and try to analyze their pros and cons. Still as the title reads the best automated deployment tool is the one that best fits your needs.

"This feature we deployed last week was working fine till yesterday now I have no idea why is it not working!" This is like a typical sentence you hear from developers when there is no logging in place. It can be to a great extent solved by having automated tests, still having logging and monitoring gives you a different viewpoint. In this post, I am going to reveal the importance of having logs for your code and monitoring your code to cut down the firefighting time for bugs and errors by huge margins.