https://jessed.io/ Recent content on SRE - Data - Systems - Code Hugo -- gohugo.io en-us Wed, 13 Jun 2018 16:57:00 -0700 https://jessed.io/post/20180427_complex_adaptive_systems/ Wed, 13 Jun 2018 16:57:00 -0700 https://jessed.io/post/20180427_complex_adaptive_systems/ 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. If you consider our anatomy, we have redundant systems: 2 lungs, 2 kidneys, 2 halves of the brain, 2 arms, 2 legs, etc. In cases where one of the components is degraded, the other component is able to pick up some of the slack to sustain life. https://jessed.io/post/20161114_5_cli_tools_all_software_engineers_should_know_about/ Mon, 14 Nov 2016 22:07:24 -0800 https://jessed.io/post/20161114_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. 5. xargs xargs simply takes strings separated by whitespace and passes those into the command specified. A simple example would be: https://jessed.io/post/20161019-fixed-vs-growth-system-failures/ Wed, 19 Oct 2016 11:06:08 -0800 https://jessed.io/post/20161019-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. https://jessed.io/post/20161004-go-is-for-closers/ Tue, 04 Oct 2016 10:35:32 -0800 https://jessed.io/post/20161004-go-is-for-closers/ In Go the typical way to open a file or connection is this commonly seen block of code: connection, err := net.Dial("tcp", "example.com:80") if err != nil { // Do something to handle the error return } defer connection.Close() That defer connection.Close() on line 6 plays a vital role in writing Go code that won’t run your host machine out of memory, kernel file descriptors, or any other transactional resource (one in which operations open, do something, then close). https://jessed.io/post/20160916-whos-running-that-on-my-system/ Fri, 16 Sep 2016 01:11:56 -0700 https://jessed.io/post/20160916-whos-running-that-on-my-system/ 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. https://jessed.io/about/ Tue, 23 Aug 2016 22:23:26 -0700 https://jessed.io/about/ I am a lead site reliability engineer at InVisionApp with over 8 years of experience. I love building platforms to support running resilient software in production. I love taking existing services and writing intelligent code to support the operations of those services. I have experience with Docker and technologies designed around Linux containers, AWS, cloud native architectures, microservices, monitoring, and automation. While I write code mostly in Go and Python. I have been known to get into Java, C, and Ruby to get things done.