Josh Feierman

5 of 5 stars to The Stone Sky by N.K. Jemisin goodreads.com/review/show/55…

5 of 5 stars to The Obelisk Gate by N.K. Jemisin goodreads.com/review/show/54…

5 of 5 stars to The Fifth Season by N.K. Jemisin goodreads.com/review/show/51…

4 of 5 stars to 1Q84 by Haruki Murakami goodreads.com/review/show/46…

4 of 5 stars to A Gentleman in Moscow by Amor Towles goodreads.com/review/show/51…

4 of 5 stars to Sword of Destiny by Andrzej Sapkowski goodreads.com/review/show/51…

5 of 5 stars to The Hero of Ages by Brandon Sanderson goodreads.com/review/show/50…

5 of 5 stars to Project Hail Mary by Andy Weir goodreads.com/review/show/49…

5 of 5 stars to The Well of Ascension by Brandon Sanderson goodreads.com/review/show/48…

4 of 5 stars to A Place of My Own by Michael Pollan goodreads.com/review/show/15…

5 of 5 stars to Mistborn by Brandon Sanderson goodreads.com/review/show/47…

5 of 5 stars to A Swiftly Tilting Planet by Madeleine L'Engle goodreads.com/review/show/43…

5 of 5 stars to Leviathan Falls by James S.A. Corey goodreads.com/review/show/44…

4 of 5 stars to This Is How You Lose the Time War by Amal El-Mohtar goodreads.com/review/show/41…

Moral of the story: idempotent code is good, therefore use existing tools where you can that have it built in, and only try and roll your own when you absolutely must.

Here's the good thing though: most good infrastructure-as-code tools have this built in! If you use Terraform, for example, and use it properly (I'm looking at you null resources), then it by-and-large ensures your code is idempotent without any effort from you.

One of the most important words in infrastructure as code development is... idempotent. What's it mean? 🧵 👇