The Unicorn Project # Since Gene Kim just came out with a new book (topic for another coffee read) I realized I never summarized his last one. So for this coffee read I chose to focus on The Unicorn Project.
The book came out in 2019 and it is a fictionalized story about a DevOps transformation taking place at the same time as The Phoenix Project with the following premise:
For this coffee read, I wanted to write about the STRIDE model and how, when working in your day to day job, you can use it to break down a functionality or requirement you may have and identify potential security threats.
The blog post is more of a guide in how create a security first mindset to approach your work. It’s not a guide on how to implement security measures or how to fix the threats (which I will add as part of tech articles). It’s more about how to identify them and categorize them.
For this coffee read, I will be reviewing the book Software Architecture Patterns (Report) by Mark Richards.
I want to start with a disclaimer on this one. I have not worked as a software architect. So this book review will be from the perspective of someone that has worked as a DevOps engineer (more of a Cloud Engineer if we have to label it), and that has been involved in the design of systems and the architecture of systems. My personal belief is you need to have a good high-level view of the system you are working on, regardless of the project or your skillset (or job title), in order to be able to design or test solutions that make it scalable, reliable, and maintainable.
If you work with real data and customers you will have to deal with customer support tickets. This is a very important part of your business and you should take it seriously. In this article, I will give my lessons learned and some tips on how to handle customer support tickets.
What is a customer support ticket? # A customer support ticket is a question, a bug report, a feature request or a complaint coming from a customer of your product. It is a communication channel between you and your customer. These complaints are logged in a ticketing tracking system such as JIRA. Generally, the expectation is to handle these tickets promptly and to make sure that your customer is happy.
For the first book review in what I will call my coffee reads section of the blog I will be reviewing the book Observability Engineering: Achieving Production Excellence.
Observability Engineering: Achieving Production Excellence # The book, in its own description, sets out to be an advocate for the adoption of observability practices in the software industry. Written by Charity Majors, Liz Fong-Jones, and George Miranda from Honeycomb.io, the book aims to be a resource for anyone interested in learning more about what is good observability, how you can build on top of your system today, and how to implement it in your organization.
