Introducing Better Practices
Postman is a developer-first company. A few years ago, community discussions centered around how individual developers could use Postman more effectively. Over the past few years, we introduced a number of features for larger teams. Since then, a big part of our daily conversations shifted away from the individual developer towards how larger teams use all sorts of tech to be more effective in their everyday lives.
What started as a specialized app for developers to send client requests saw quick adoption by Testers, DevOps, and quickly grew into a diverse community of over 6 million Postman users who interact with APIs in one way or another.
We found ourselves in the lucky spot of working with so many of the most progressive engineering teams in the world. Furthermore, these teams freely shared their insights and workflows with us. We were able to identify the common threads across these industry leaders, and the aha moments were happening faster and faster.
But we didn’t have a great place to share this with the rest of our community.
We already had a Postman blog, where we announce company updates and talk about all the Postman things, but this wasn’t the right place to go deeper into specific topics and talk about innovative workflows and concepts. So we decided to launch a new engineering blog, but wanted it to encompass more than “just Postman stuff” and also to share valuable insights with our community who was more than “just engineering”.
Introducing the Better Practices publication!
For individual engineers to the largest teams, Better Practices is intended to distill knowledge from this community that we are so lucky to be a part of. We also hope this will spark some online conversations that mirror the ones that we’re already having face to face.
Why not call it “Best Practices”?
We chose “better”, and not “best”, primarily for two reasons.
- What works for one organization may not be the right fit for another. Our goal is to share broader perspectives and show you at least one way to implement a workflow. The approach you choose will ultimately be determined by your team’s current infrastructure, capabilities, and business goals.
- What might be considered a “best practice” today may not be the best tomorrow. Since the world continues to evolve, and as more people are willing to talk about their own better practices, we can build on this shared knowledge and foster innovation at a faster rate.
What can we look forward to?
- Thought-leadership pieces from the Postman engineering team, guests with a unique perspective, or distilled from the broader community
- Recipes showcasing at least one way to implement a workflow
- Data-driven analyses about workflows from around the world
We want to hear about your better practices, too. If you have ideas about what you’d like to read, let us know what you’re thinking @postmanclient on Twitter. And if you’d like to submit an article, we’d love to hear about it.
Welcome, and come on in!
We hope you enjoy Better Practices — a place where we can learn about modern software practices together! And while you’re here, go ahead and hit that Follow button, so you’re first in line to see what’s new.
