David Sachdev

As a Software Architect that has spend the last handful of years with a strong focus on the DevOps and Cloud world, it will be very interesting to see your approach to the task.  I'm curious how much of the book focuses in on MicroServices, and how to migrate there - and if there is a focus on greenfield MicroServices development.  Looking over your tools most are familiar, but some are new to me - and I'm looking forwared to digging into some of those new tools and digging in.

Henry Wong wrote:
This week, we're delighted to have Jamie Riedesel helping to answer questions about the new book Software Telemetry.

Welcome Jamie!  I look forward to getting into the discussion and knowing what tools that you recommend!

Thank you for starting your book out on the reasons for choosing Rust, and its benefits over other choices. I did not some interesting things such as the return of the "struct" and the use of words that other languages have reserved such as "new". Hoping that syntax is pretty easy to use, and not too complicated when hoping between languages. It did bring up one question, and one comment:

1) I'm curious to know what your previous preferred languages are/were?  What have you tended to program in
2) The preview of the first few chapters using the app linked here seems to be translating the book in real-time.  Was it written in English first (I assume yes, because it reads easily) but I have seem a few glitches where there are paragraphs that are not translated...just thought I might mention that...and now that I'm saying it - maybe it is an encryption of some sort...I should copy/paste and review the "non-English" a bit closer.  

Thanks
David Sachdev

Welcome to the Ranch....I don't know much about Rust, but I'm hoping to have some time to read a bit and learn.  Hope to get some questions/dialogue up later.

Thanks
David Sachdev

One of the issues we have found with Terraform scripts is that they can be complex, and while they are designed to help remove that complexity (and in theory make things repeatable, documented, and portable) there are also compliance and security concerns.  Unless you thoroughly understand what a terraform script is doing, you may violate your agency's security polices on things such as creating open gateways or the like.  How do you suggest getting a deep understanding of everything that the terraform script is doing while you are learning terraform and utilizing open source terraform scripts?

Thanks
David Sachdev

Stephan van Hulst wrote:You're not nearly too late for this year. Work on the puzzles that have already been released to catch up, and you can still easily score a nice ranking if you keep up with the puzzles that are yet to come.

I went back through the last few years, and on average day 16 is my breaking point. I've never even started a puzzle after day 20.

Thanks for the insight - I've been checking out the website!

Thanks
David

Thank you!  That is a lot of insight that you don't often have when you pick up a book - and you wonder why they author made the choices that they did.  It is helpful going in knowing the timeframe and the tech as the time...as our field is always moving....and technology becomes ancient quickly.

Thanks
David Sachdev

wow, I'm just learning about this.  I guess I'm pretty late, but want to read up and join in next year!

David

Scott Winkler wrote:

The world of Terraform has changed a lot even since I wrote the book. But I feel it is still the best resource available for someone wishing to improve their skills with Terraform. The HashiCorp documentation is great, but scattered. Other books and video courses don't go into enough depth. The reason this book is valuable is because it is highly opinionated and providers the reader a distinct learning path to becoming an advanced Terraform user.

I hope this answers your question.

Regards,
Scott

I see that the book is from May 2021, but of course the editing phase takes its time - how up to date would you say the book is?  Is there a particular version you would say that the book covers up to?

Also, as far as integration with other infrastructure as Code tools (Chef, Ansible, etc) do you cover that in the book - and talk about what aspects of the CI/CD pipeline you would "relinquish" to what tools?

Thanks
David Sachdev

Scott Winkler wrote:Y


If you do find some situation where Terraform doesn't quite do what you need it to do, there are always bandaids like the External https://registry.terraform.io/providers/hashicorp/external/latest/docs or Shell https://registry.terraform.io/providers/scottwinkler/shell/latest providers for Terraform.

Thank you - I am not familiar with these, and will check them out!

Given AWS's tendency to constantly release new products, do you provide a good list/resource of knowing what new AWS resources and services are not covered/managed by Terraform yet, and how long of a lead-time it takes for new resources to be brought into Terraform?  Also, do all the clouds need to have a comparable resource for it to be covered by Terraform?

I am curious to know how much your book touches on how well Terraform interacts with the other HashiCorp products - in particular Vault, but I am also very interested in Boundary and where it is going to go.  Do you see Terraform as more as a "get stuff started" and move on tech, or do yo see it as part of your ongoing activities - and continuous monitoring type tasks?

I'm curious how well your book covers the differences between the clouds - and if there is a focus in particular on some of the clouds.  

Welcome - looking forward to learning more about your book and Terraform in general!