A Keyhole Consultant was brought in to directly work with the client’s full-stack development team. The goal of the project was to help the client implement new features for their application. This resulted in the implementation of a new GraphQL API and architecture for multiple interdependent systems. Keyhole Software was responsible for coaching the client’s development team in React best-practices, and working with them to refactor the code to align with those best practices.
Apple Silicon for Development
In June, Apple announced a two-year transition from Intel to Apple Silicon for the iMac and MacBook line. I knew Apple had lost their mind. But, before Christmas, I owned my very own chunk of Apple Silicon living in an attractive milled-aluminum case.
In this article, I’ll discuss the Apple M1 silicon-on-a-chip (SoC) used as a software development computer. I’ll cover installation, and I’ll also talk through running apps that support development on my M1.
JavaScript Shortcuts from a Seasoned Professional
I’ve spent the past 15 years of my career working as a web developer. Over those years, I’ve learned and created various shortcuts to help ease development. So, I figured I’d share them with you. This short write up lists some of the JavaScript tips and tricks that I’ve picked up during my career.
The first snippet I’ll cover is one I’ve only used in a very specific, unique circumstance. It may not be relevant to all of you, but I wanted to share for the few it would apply to. The rest are snippets I use on nearly a daily basis. No matter your situation or requirements, you should be able to find at least one that you can adopt.
Using Jest and Testing Library with React Native Part II: Our First Test
This is Part 2 of our series, Using Jest and Testing Library with React Native. This post will cover the steps you’ll need to take to write your first test. We will also break down the code line-by-line, so you have a clear understanding of the process.
Infrastructure as Code Using Azure CLI
Infrastructure as Code (or IaC) is the process of using code and versioning in the same way you do your source code to manage your networks, VMS, and Azure resources. IaC generates the same environment every time it is applied, and it’s an important DevOps practice to use alongside continuous delivery.
The release pipeline executes this model to configure target environments. If you need to make any changes, you edit the source, not the target environment. This allows you to create reliable and stable environments on-demand that can be validated, tested, and repeated.
In this blog, we’ll look at how we can use Azure CLI and Azure DevOps Release Pipelines to make this happen. I’ll walk you through all the steps you need to take to get set up.





