In this post, l explain how we used Visual Studio Code’s Development Container feature as a stepping stone in our long-term effort to achieve Collaborative Infrastructure as Code. This one step in the process gave a versioned, repeatable working environment and allowed us time to determine the next steps in the effort to achieve IaC.
Keyhole Software is pleased to announce the expansion of its business development team with Zach Johnstone in Denver, CO and Katye Moore in St. Louis, MO. Johnstone and Moore bring essential skills in business development and sales and operation planning to the Keyhole team. They will not only expand Keyhole’s presence in growing territories but provide support to a highly skilled team on a mission to deliver custom software solutions to their clients.
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.
Attention: This article was published over 5 years ago, and the information provided may be aged or outdated. While some topics are evergreen, technology moves fast, so please keep that in mind as you read the post.We are excited to announce that Keyhole Software is a Red Hat Ready Partner. This collaboration with Red Hat indicates Keyhole Software’s commitment to …
It can be rough to ask your development team to estimate work based on abstract story point values, especially when they are new to it or to each other. I know this and have experienced this in full.
So in this blog, I am going to share an exercise with you that will give every member of your team the same frame of reference for estimating the size of their work. I call this exercise Story Point Benchmarking.