Atlassian to shed 5 per cent of workers

Re:Atlassian to shed 5 per cent of workers by ejb999 on Tuesday March 07, 2023 @07:46AM (#35054691)

I actually find postman quite useful for the work I do (heavily api-related) - if you work in that space, what other tools would you recommend instead?

[ Parent | on HN ]

Re:Atlassian to shed 5 per cent of workers by kimburgess on Tuesday March 07, 2023 @08:28AM (#35055071)

IMO Postman is a good tool. On alternatives though, https://httpie.io/ is pretty nice too.

[ Parent | on HN ]

Re:Atlassian to shed 5 per cent of workers by philliphaydon on Tuesday March 07, 2023 @08:14AM (#35054950)

I use insomnia after the stunt postman pulled with pricing.

[ Parent | on HN ]

Re:Atlassian to shed 5 per cent of workers by pxc on Tuesday March 07, 2023 @10:12AM (#35056183)

Insomnia seems like a good replacement for web devs who don't want to rely on proprietary tools as part of their core workflow, as well.

I like HTTPie and HTTPie/http-prompt as well.

[ Parent | on HN ]

Re:Atlassian to shed 5 per cent of workers by rukshn on Tuesday March 07, 2023 @07:55AM (#35054770)

I use https://hoppscotch.io/ as a replacement for postman

And also ThundeClient a VS Code extension when using VS code.

[ Parent | on HN ]

Re:Atlassian to shed 5 per cent of workers by XorNot on Tuesday March 07, 2023 @08:16AM (#35054968)

Honestly? Jupyterlab with python and requests.

It'll do more, with richer libraries, and an obvious path towards automation into CI/CD.

[ Parent | on HN ]

Re:Atlassian to shed 5 per cent of workers by porker on Tuesday March 07, 2023 @09:36AM (#35055772)

The problem I've had with Postman is the sharing between team members. Everyone needs to add new requests, edit (locally) but sometimes sav the edits back to the collection.

Someone has to modify the auth script and have it update for everyone.

I thought this is what the tool is designed for, but it's been a nightmare. Team members have to wipe their environment and start again regularly. I want to think that we've completely mucked up using it but I'm not sure it's us and not the tool.

[ Parent | on HN ]

Re:Atlassian to shed 5 per cent of workers by ben7799 on Tuesday March 07, 2023 @10:56AM (#35056788)

I use Postman all the time for work and it is definitely useful.

But it seems to be getting worse not better as they tack on more features and make it more complicated.

It seems like it's been years since they added anything I need and instead it has just gotten harder to use due to extra fluff. And it's buggier than it's ever been.

[ Parent | on HN ]

Re:Atlassian to shed 5 per cent of workers by bydlocoder on Tuesday March 07, 2023 @01:12PM (#35058845)

Apparently, they decided that selling merch is more important than implementing gRPC support.

[ Parent | on HN ]

Re:Atlassian to shed 5 per cent of workers by systematical on Tuesday March 07, 2023 @01:55PM (#35059504)

I do work in that space. I build APIs and I use them. I built a springdoc for php so I know a bit about what I am talking about: https://github.com/cnizzardini/cakephp-swagger-bake

The Postman UX is not good on it. It's easy to get lost in tabs, they should ditch the tabs and categorize requests under the actual endpoint. There is also no way to easily save like requests and give them better names that is also searchable. It's also built on electron which means its slow and clunky.

There is nothing good in this space. Swagger would do it if they let you save requests to local browser storage and just added a history dropdown to the endpoints. I use swagger and save common requests to a file system and open them in sublime. if its just JSON payloads I am working with it does the job.

[ Parent | on HN ]