Recent content on Gary's Blog
The thing that should have been a 2 a.m. incident 
 You wire a database tool into your coding agent. PostgreSQL, Databricks, an internal HTTP API — whatever. The agent is useful . It joins tables you’d forgotten existed, drafts the migration, and writes the report. Productivity goes up.
The problem 
 Most regulated software environments require a Change Request before any production deployment. The CR needs a list of every JIRA issue included in the release — what changed, why, and who approved it.
TL;DR 
 
This is the story of how we improved our CI/CD methodology by using Bamboo-on-Teams , a serverless ChatOps tool for interacting with Atlassian Bamboo from Microsoft Teams. 

Shifting from monolith architecture to microservices are full of challenges where one primary is how to manage security and access control properly. As each microservice is running indenpendly and communicates with each other to perform a specific function, we need to authenticate the incoming request to ensures that it comes from a legitimate service.
Background 
 
There was a time when I was working on a feature which required changes to more than ten microservices. In the dev testing stage I got all the services up running in the cloud by applying Cloudformation changes from local. To simplify the work, I had one command prompt opened for each service so that I can build, package and deploy it whenever I changed something.
Recursion provides us an easy way to solve some problems, and makes the code simpler and easier to follow. But one problem of it is the memory cost caused by the recursive call stack, which could be critical for memory sensitive applications like mobile ones.