<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SoftwareYoga</title>
    <link>https://www.softwareyoga.com/</link>
    <description>Recent content on SoftwareYoga</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 04 Mar 2020 22:08:47 +0000</lastBuildDate><atom:link href="https://www.softwareyoga.com/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>About</title>
      <link>https://www.softwareyoga.com/about/</link>
      <pubDate>Wed, 04 Mar 2020 22:08:47 +0000</pubDate>
      
      <guid>https://www.softwareyoga.com/about/</guid>
      <description>Hi. I&amp;rsquo;m Deepak I&amp;rsquo;m the owner and content creator at SoftwareYoga.com. I have been involved with the software industry for over 15 years. I have held numerous positions over the course of my career that included responsibilities in software development and technical leadership.
My specialization is in building large enterprise systems that are scalable, highly available and extensible, primarily using Java and related technologies.
I have mentored in-house and offshore development teams on software architecture principles, coding standards, writing effective use cases, test methodologies, Agile and Scrum practices etc.</description>
    </item>
    
    <item>
      <title>Metrics - Measuring Continuous Delivery</title>
      <link>https://www.softwareyoga.com/metrics-measuring-continuous-delivery/</link>
      <pubDate>Mon, 10 Dec 2018 09:44:28 +0000</pubDate>
      
      <guid>https://www.softwareyoga.com/metrics-measuring-continuous-delivery/</guid>
      <description>This post was originally written for TechTownTraining blog.
This is Part 4 in the series on Continuous Delivery. In previous parts, we introduced to you the concept of continuous delivery, how you can prepare your organization for adopting CD and also defining your product architecture to easily support a Continuous Delivery development model.
In this article, we&amp;rsquo;re going to discuss about Continuous Delivery metrics. With proper measurement of various metrics during the process of adopting Continuous Delivery, you can correct your course of make necessary adjustments to your plans at any stage.</description>
    </item>
    
    <item>
      <title>Deploying Your First Web App to Tomcat on Docker</title>
      <link>https://www.softwareyoga.com/docker-tomact-tutorial/</link>
      <pubDate>Thu, 01 Nov 2018 13:30:17 +0000</pubDate>
      
      <guid>https://www.softwareyoga.com/docker-tomact-tutorial/</guid>
      <description>This post was originally written for TechTownTraining blog.
Docker is a platform for developers and sysadmins to develop, deploy, and run applications with containers. As we explained in the previous post, Docker containers wrap up software and its dependencies into a standardized unit for software development that includes everything it needs to run: code, runtime, system tools, and libraries.
In this post, we are going to step through a basic tutorial on getting a web application running on Tomcat Docker Container.</description>
    </item>
    
    <item>
      <title>Architecture for Continuous Delivery</title>
      <link>https://www.softwareyoga.com/architecture-continuous-delivery/</link>
      <pubDate>Wed, 24 Oct 2018 22:44:28 +0000</pubDate>
      
      <guid>https://www.softwareyoga.com/architecture-continuous-delivery/</guid>
      <description>This post was originally written for TechTownTraining blog.
This is Part 3 in the series on Continuous Delivery. In Part 1 and Part 2, we introduced to you the concept of Continuous Delivery and how you can prepare your organization before adopting CD practices.
In this article, we&amp;rsquo;re going to discuss about architecture for continuous delivery. How do we architect our systems in a way that enables us to continuously deliver value to our customers?</description>
    </item>
    
    <item>
      <title>Are You Prepared for Continuous Delivery?</title>
      <link>https://www.softwareyoga.com/prepare-for-continuous-delivery/</link>
      <pubDate>Wed, 10 Oct 2018 22:44:28 +0000</pubDate>
      
      <guid>https://www.softwareyoga.com/prepare-for-continuous-delivery/</guid>
      <description>This post was originally written for TechTownTraining blog.
This is Part 2 in the series on Continuous Delivery. In Part 1, we introduced to you the concept of continuous delivery, how it is related to continuous integration and the advantages it brings to the table.
Continuous Delivery requires that every commit into the code base be built immediately and that any build can be deployed into the production environment.
So now that you have decided to implement Continuous Delivery practices, I thought I’d share a few ways in which you can begin making the transition to Continuous Delivery.</description>
    </item>
    
    <item>
      <title>Continuous Delivery - A Step up from Continuous Integration</title>
      <link>https://www.softwareyoga.com/continuous-delivery-step-up-from-ci/</link>
      <pubDate>Sat, 15 Sep 2018 22:44:28 +0000</pubDate>
      
      <guid>https://www.softwareyoga.com/continuous-delivery-step-up-from-ci/</guid>
      <description>This post was originally written for TechTownTraining blog.
In this series of posts, we will take a look at how to extend and build on your existing Continuous Integration (CI) infrastructure and processes towards a Continuous Delivery (CD) model.
In this article, we will go through the basics of CD, it’s relation to CI and its importance in the software delivery model. Additionally, the purpose of this post is to point out the key elements and differences between continuous integration and continuous delivery.</description>
    </item>
    
    <item>
      <title>6 Reasons why DevOps transformations fail</title>
      <link>https://www.softwareyoga.com/6-reasons-devops-transformations-fail/</link>
      <pubDate>Sat, 09 Sep 2017 10:52:31 +0000</pubDate>
      
      <guid>https://www.softwareyoga.com/6-reasons-devops-transformations-fail/</guid>
      <description>This post was originally written for TechTownTraining blog. You can find the original article here
Introduction DevOps is the hottest buzzword in the world of service delivery. More and more organizations are jumping onto the DevOps bandwagon in the hope of transforming their broken product delivery pipeline.
And yet, not many people know what exactly DevOps is.
Is DevOps about technology? About process? About people?
Founders of DevOps coined the acronym “CAMS” to describe the aspects of DevOps – “Culture, Automation, Measurement, and Sharing”</description>
    </item>
    
    <item>
      <title>Why Automation Testing is Necessary?</title>
      <link>https://www.softwareyoga.com/automation-testing-necessary/</link>
      <pubDate>Sat, 09 Sep 2017 10:41:40 +0000</pubDate>
      
      <guid>https://www.softwareyoga.com/automation-testing-necessary/</guid>
      <description>This post was originally written for TechTownTraining blog. You can find the original article here
Introduction Automation testing is the application of tools and technology to testing software with the goal of reducing testing efforts, delivering capability faster and more affordably. It helps in building better quality software with less effort.
Many companies are already using automation testing to a certain extent, but still largely depend on manual tests because they don’t know how to properly leverage the benefits of automated testing in their development process.</description>
    </item>
    
    <item>
      <title>Continuous Integration (Part 3) – CI Best Practices</title>
      <link>https://www.softwareyoga.com/continuous-integration-part-3-best-practices/</link>
      <pubDate>Thu, 10 Aug 2017 22:44:28 +0000</pubDate>
      
      <guid>https://www.softwareyoga.com/continuous-integration-part-3-best-practices/</guid>
      <description>This post was originally written for TechTownTraining blog. You can find the original article here
Introduction This is Part 3 in the series on Continuous Integration. In this article, we will go through the best practices of implementing a CI process. I’ll also cover some real world tips and warnings based on my experiences in the industry.
A quick recap: In Part 1 of this series, we covered the basic concepts of CI and its relevance in an Agile and DevOps team culture.</description>
    </item>
    
    <item>
      <title>Continuous Integration (Part 2) – CI Server &amp; Tools</title>
      <link>https://www.softwareyoga.com/continuous-integration-server-tools/</link>
      <pubDate>Sun, 18 Jun 2017 23:39:57 +0000</pubDate>
      
      <guid>https://www.softwareyoga.com/continuous-integration-server-tools/</guid>
      <description>This post was originally written for TechTownTraining blog. You can find the original article here
Introduction In the previous post in this series on Continuous Integration (CI), we looked at the basic concepts of CI, how it helps in reducing faults while integrating software, the advantages and difficulties in adopting it and finally, how it can benefit in enforcing an Agile and DevOps team culture.
We also discussed the most common ways in which the CI fits into the development process, resulting in improved software quality, faster time-to-market, quicker feedback cycles and lower costs of development.</description>
    </item>
    
    <item>
      <title>Continuous Integration – Introduction</title>
      <link>https://www.softwareyoga.com/continuous-integration-introduction/</link>
      <pubDate>Mon, 29 May 2017 00:28:32 +0000</pubDate>
      
      <guid>https://www.softwareyoga.com/continuous-integration-introduction/</guid>
      <description>This post was originally written for TechTownTraining blog. You can find the original article here.
Introduction Continuous integration, referred to in short as CI, is a technique developed by Grady Booch in which developers are encouraged to continually merge their code into the main source code repository.
Each of these ‘merges’ or ‘commits’ into the repository is usually followed by a series of automated tasks: compilation of code, execution of unit tests and integration tests, static code quality analysis to determine whether the code quality has degraded etc.</description>
    </item>
    
    <item>
      <title>Microservices: Pros and Cons of Mono repos</title>
      <link>https://www.softwareyoga.com/microservices-pros-cons-mono-repos/</link>
      <pubDate>Tue, 26 Jul 2016 22:51:11 +0000</pubDate>
      
      <guid>https://www.softwareyoga.com/microservices-pros-cons-mono-repos/</guid>
      <description>Recently, there was an interesting question on Quora on Microservices - What companies use a mono repo but deploy as microservices?
The real question is hidden behind those words - Is it ok to use Mono repos to store Microservices code?
At first sight, it appears that Microservices and Mono repos are at odds with each other. Does it make sense to have Microservices code in a mono repo when they are going to be deployed independent of each other?</description>
    </item>
    
    <item>
      <title>3 Reasons Why People Write Insanely Bad Code</title>
      <link>https://www.softwareyoga.com/3-reasons-people-write-insanely-bad-code/</link>
      <pubDate>Tue, 28 Jun 2016 20:15:18 +0000</pubDate>
      
      <guid>https://www.softwareyoga.com/3-reasons-people-write-insanely-bad-code/</guid>
      <description>Ever Wondered Why You See Bad Code Everywhere..?
I have been contemplating over the last number of days as to why we as an industry keep producing bad code all the time.
 The number of developers who are able to build systems with high quality code are far and few in between, as the cliche goes, like a needle in a haystack.
1. The Obvious Reason&amp;hellip; The most obvious reasoning I could imagine are that there are good programmers and not-so-good programmers, there are people who are at a higher skill level and those at lower levels, there are people interested in the craft and the rest who don&amp;rsquo;t care much more than the pay-check&amp;hellip;.</description>
    </item>
    
    <item>
      <title>Performance and Monitoring Guide from DZone</title>
      <link>https://www.softwareyoga.com/dzone-performance-and-monitoring-guide/</link>
      <pubDate>Wed, 01 Jun 2016 23:03:09 +0000</pubDate>
      
      <guid>https://www.softwareyoga.com/dzone-performance-and-monitoring-guide/</guid>
      <description>My contribution to DZone Performance and Monitoring Guide I am delighted to announce that I am a featured author in DZone Performance and Monitoring Guide that released recently.
Download Now!  
This guide contains everything from finding the root cause of a performance issue to designing parallel algorithms.
Find out what 600 developers (including myself) have to say about monitoring, database performance, application logs, multi-threading, and more. Discover some important latency numbers so you can troubleshoot performance problems and prevent future bottlenecks.</description>
    </item>
    
    <item>
      <title>Technical Leadership in Software Companies</title>
      <link>https://www.softwareyoga.com/technical-leadership-software/</link>
      <pubDate>Tue, 31 May 2016 15:57:20 +0000</pubDate>
      
      <guid>https://www.softwareyoga.com/technical-leadership-software/</guid>
      <description>Recently I was invited as a speaker in one of Ireland’s largest technology event, Tech Connect, held in Dublin on the 25th of May 2016.
It is a gathering of 3000+ key decision makers from the Irish and international tech sector and provides an unique forum for technology companies, start-ups and investors.
I spoke on the topic of &amp;ldquo;Technical Leadership in Software Companies&amp;rdquo;. The talk was well received from the audience and gave them something to think and act upon.</description>
    </item>
    
  </channel>
</rss>
