![]() ![]() My first entry point into using API-first was for the RESTful API I built for a fitness-based service I created with my sister-in-law. With the success of the API in the early 2000s by companies like Salesforce and eBay, the concept of API-first – defining your API specification before any coding begins – did not become mainstream until about five years later. Today, as a service developer, I see Postman’s in multiple places during the API life cycle. This approach allowed me to write a given request one time and be able to use the same request in every application environment – from local to development and even production. As a result of the simple-but-effective user interface, my requests were presented in a better light and easily cloned to further exercise my services.Īs I gained experience using Postman, I added environments and variables to my requests and started grouping them in collections that were much easier to reference. With the Postman app installed in Chrome, I was able to onboard quickly by importing those cURL commands from my Notepad document. Just recapping that time of my life sends chills down my spine. Using a cURL command from my Windows-based developer machine was painful to say the least, relying heavily on copying and pasting from a Notepad document I kept on my desktop. When I started using Postman in 2014, I was in dire need of a better way to exercise my APIs. If you are interested in the evolution of Postman, check out The New Postman API Platform: Redefining API Management for the API-First World. ![]() Incredibly, 98% of today’s Fortune 500 companies are using Postman. Here’s an example of what Postman looked like back then:įast-forward to today where Postman is a standalone client used by over 25 million developers globally and half a million companies, including Box, LinkedIn, Paylocity, Paypal, Sling, Twilio, Twitter/X, and WhatsApp. At the time I started using Postman, it was a free plugin that I could use within my Chrome browser. Postman started as a side project of software engineer Abhinav Asthana, with a goal to simplify the API testing process. In a bit of a personal retrospective, I wanted to talk about how Postman has helped me to build thriving APIs and to succeed while working in a 100% remote environment. Aside from the IntelliJ IDEA integrated development environment (IDE), Postman was a critical tool that helped me become successful as a service developer and architect. I also realized which tooling dependencies I leaned on to help me to become more productive. I also felt like the quality of my work improved, largely because of the ability to place myself in focus mode, devoid of any unexpected distractions. Just under 3 years before the pandemic arrived, I discovered I was twice as productive as before – simply by reviewing my commit history from in-office time periods where I was doing similar work. After 25 years of working in technology across eight different employers, I was finally able to determine if working 100% remotely would lead to productivity gains … or losses. When summer of 2017 arrived, I transitioned to a project which allowed me to contribute remotely. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |