👋 Hello, world! Welcome to the TROUBLESHOOTING PARTY 🎊!
In tech, we talk a lot about troubleshooting specific problems. I am eager to foster conversation around strengthening general purpose troubleshooting tools that can be applied broadly. On troubleshooting.party, I hope to explore patterns, practices and examples to help make difficult problems easier to approach. The six principles in the blog post should help 🚀 us get started!
- See 🔬 GraphQL - gathering query complexity information for an example of how to apply the
increase verbosityprinciple. The information in this practical example may be of use to those who troubleshoot Web or mobile applications that make or rely on GraphQL queries. - Use api.troubleshooting.party while learning
gron, a super useful tool for usinggrepwith JSON — and avoiding the need to usejq. This is useful for a variety of purposes including inspecting API responses. - IN PROD WE TEST is a “build in public” test lab used to explore different troubleshooting tools.
I’m also collecting external sources of general troubleshooting info.
- Effective Troubleshooting chapter from Google’s SRE book
Who hosts the troubleshooting.party?
Oh, hi! My name is Brie and you can find me all over the Web!
- 📖 You can read what I’ve written at brie.dev or briecarranza.com — or any one of my other blogs.
- 📯 You can follow me on Mastodon. I’m most active on social.lol/@brie. Some things are posted automatically at brie.lol/@brie.
- I would love to hear from you if you find anything here useful or if you have suggestions!
- 💼 I am also on LinkedIn.
💖 Enjoy!