Sounds great in theory, but without a concerte suggestion on how that might actually work and be implemented it's basically a scifi daydreaming nothingburger. (Or the pitch for the writers upcoming startup)
There is Bruno, which is git based (also its FOSS). We use it in our team for a few months now and the git model is well suited to the context.
As far as I can see it is still just postman but the request and api definitions are stored in textfiles (and there are multiple projects that do exactly that already).
It seems to me that the blog author is talking about something beyond that.
Maybe. But then I don't get their point tbh
Just in case you wanna try it out : https://voiden.md/
We have a very different approach to API tooling.
I knew it ...
Slack did not replace email by becoming a slightly better inbox.
In what universe has Slack replaced e-mail?
Honestly? In the startup Universe. People at my company have to be reminded to check their email.
The vast majority of customer interaction where I work is through Slack or Discord. Companies buy support plans just to get a Slack channel where they can tag their favourite support person / migration services person / the CEO.
We're mostly Millenials or thereabouts but we're talking to Gen Z / Gen A and you gotta meet people where they are. For better or worse, that's meant a lot less email.
In some companies, Microsoft Teams has replaced in part e-mail, so that an email became a message on a shared channel.
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev