SRE - Data - Systems - Code
My personal blog where I talk about site reliability engineering, DevOps, Go, and software systems.
Giving VSCode a go
I tried VSCode for 3 weeks just because I had been working a lot with Terraform and other members of my team mentioned the various plugins available for Terraform. I found using VSCode to be a really wonderful experience.
Complex Adaptive Systems in Software
Resilience engineering is becoming a required practice as people begin to expect services to be available nearly 100% of the time. We have the same requirements of the systems that sustain us: ecosystems, anatomical systems. Our world is one complex adaptive system after another.
5 CLI Tools all software engineers should know about
The following CLI tools, I have found to be extremely useful when dealing with systems to quickly find the information I need. Please note that all these commands are being run from OS X and are the BSD commands not the GNU commands that typically ship with a standard Linux distro.
Fixed vs. Growth System Failures
The concept of Mindset based on the work: Mindset by Dr. Carol S. Dweck, Ph.D. has been around for some time now, but recently I was thinking about root cause analyses meant as a tool for learning. Revisiting the John Allspaw post: The Infinite Hows (or, the Dangers Of The Five Whys) make me start thinking about what makes a lot of people look at postmortems as a checkbox or paperwork and not value them as learning experiences.
Go is for .Close()’ers
The Close() method is important to the reliability of a running program and it’s not easy to tell when it should be used.
Who’s Running that on my System: Case of the stolen CPU
Last week, I found myself needing to find what application a query was originating from. My typical method for doing this is searching through source code before I eventually get angry that I can’t find the query originating from an ORM and start drafting an email decreeing that all applications get distinct logins to the database that I’ll never send because who is going to listen anyway. I had an idea for how I can track a query all the way back to the process that accessed it and I even scripted it.