After our first few meetings, it was clear that J.D. was the right person to architect the infrastructure for NuID. Our work together substantiated one of J.D.’s earliest claims to me: “I will be a force multiplier.”
NuID needed cloud-native infrastructure and a matching CI/CD process. That's precisely what we got.
It is difficult in systems projects to preemptively establish requirements and boundaries. The complex and often opaque relationship between technology and its environment is underrepresented or entirely absent from otherwise thorough project plans.
J.D. handles it.
His expertise throughout the development, security, and operations lifecycles, along with his capacity for design, architecture, and communication, ensured our projects achieved their mandates in full.
J.D. is exactly who you want making the decisions you can’t.
Get the latest posts from The Consulting CTO.
-
-
How to Bootstrap Multiple Environments on AWS with Terraform & Fenna
-
Terraform for Teams
An Introduction to Fenna
-
Continuous Delivery with Terraform
A NuID Case Study
-
Bastions on Demand
-
HTTP Direct with Datomic & Terraform
-
Datomic with Terraform
-
Focus As Context: How I Use OmniFocus
-
How do I structure my Terraform projects?
-
Should I use a single, monolithic Lambda function or multiple Lambda functions with API Gateway?
-
On Returning to Rails
-
Working with Terraform: 10 Months In
-
Deconstructing the CMS
-
Maximize Velocity by Minimizing Risk
-
Automated Lambda Deployments with Terraform & CodePipeline