The steps described in this blog post allow for the adding of a Logic App on Azure to append rows to an Excel file. It took a lot of trial, and mostly error, to figure out how to describe what I wanted in the way that the Logic App would understand. Hopefully, the steps that I outlined in this blog post will save others the time it took me to come up with them.
This blog is about converting legacy code better—using architecture already in place, SOLID principles, and best practices.
Generally speaking, not having an architectural plan set up (or not using SOLID principles and best practices) can lead to passing the buck to the next generation of developers. We should all strive to push good code forward to get the latest and greatest out there. Starting with following the patterns in place at your job, or SOLID best practices, will make converting and upkeep way faster in the future.
This post contains a discussion of my experience in various software team environments. Throughout them all, we show that if SOLID patterns and best practices had been followed, then time spent converting code would have been less and code upkeep would have been easier down the line.
Keyhole Consultants are currently leading an initiative at a large financial services firm to move a large, monolithic, legacy application running in the organization’s “on-premise” data center, to a microservice-based suite of applications running in the “cloud.” The application is being iteratively moved to containers, orchestrated by Kubernetes in the AWS Cloud.
The effort was centered on developing a more agile environment including process, practices, and technology choices, with the goal of cultivating a DevOps culture.
In one of my previous Spring Batch blog articles, I wrote about the need to read a set of data, process the data, and export the transformed data into XML for consumption by another system. In this blog, I’ll be doing the opposite. I’ll show you how to read data from an XML format instead.
As software developers in 100% remote work environments, we now have additional challenges stemming from the loss of face-to-face communication. In many situations, this can lead to harmful trends in coworker interactions—less job satisfaction, co-worker interactions, and overall team success. One way to combat this negative side effect of remote work is to increase Emotional Intelligence as an individual software developer.
In this blog, we discuss how interactions between software developers are affected by Emotional Intelligence (EQ). In addition to the basic components of EQ, we discuss suggestions for improving Emotional Intelligence in common interactions experienced by software developers.