zdne

9 ms·

1.
Agentic Payments: How Agents Move Money(zdne.org)
2 points by zdne 21d ago|0 comments
2.
by zdne 5y ago
Thanks for taking the time to write down your thoughts! I deeply appreciate it! My bad I was not concrete. What I've meant by "this/that" the entire "find the docs - read the docs - program/generate your client
3.
by zdne 5y ago
Is it that you disagree on the topic? There is nothing subtle about the fact that most of the API tools development goes towards fixing something that does not even have to be there.
4.
OpenAPI cures symptoms, not disease(superface.ai)
4 points by zdne 5y ago|4 comments
5.
57bn USD/year – the cost of API works(medium.com)
2 points by zdne 5y ago|0 comments
6.
Introducing Supermodel.io – Domain Modeling and JSON Schema Registry(supermodel.io)
4 points by zdne 8y ago|0 comments
7.
Deira Serverless API(deira.ai)
2 points by zdne 9y ago|0 comments
8.
Stop versioning APIs(blog.goodapi.co)
3 points by zdne 9y ago|0 comments
9.
by zdne 10y ago
Big fan of what you are doing! But can you elaborate a bit on TAM? Isn't the possible market too small? https://github.com/coffeemug/defstartup/blob/master/_posts/2...
10.
We need to break our APIs to enable autonomous AI(blog.goodapi.co)
3 points by zdne 10y ago|0 comments
11.
by zdne 10y ago
The thing is, why APIs aren't a mix of domain vocabularies? Why the isolated silos with no interlinking? The Web grew strong because sites were interlinked. REST APIs are supposed to be generalized Web and yet they are missing the link
12.
by zdne 10y ago
That's an excellent point! It's sure the case for the "building API to leverage (pardon me the word) the channels" scenario. These pre-agreed scenarios couldn't be automated. But other business drivers (direct data
13.
by zdne 10y ago
That is my point: We don't need to understand the communication means. Instead, we should just declaratively say what we want the machine to do, and it will figure out the rest.
14.
by zdne 10y ago
Yup, AGI should be able to "figure it out" at the runtime (when the two machines meet).
15.
by zdne 10y ago
The results are relevant only if 1. the name of API contains the term or affordance you want to use 2. you are a human being (you cannot perform such discovery as a machine)
16.
by zdne 10y ago
Thanks for the review! I didn't mean the article as a marketing post, but I wanted to share my (long) thought process. Nothing in the article is new in the concept, but maybe™ the time is now right. Frankly, what the part I'm conc
17.
by zdne 10y ago
Fair point! I'll try to answer with a question: So why is it that Google, Microsoft & Yahoo cooperate on schema.org to establish shared vocabulary? They don't have to make it interoperable per se. It'd be enough to use so
18.
The Future of APIs: APIs aren’t the endgame they won't stay forever(blog.goodapi.co)
95 points by zdne 10y ago|61 comments
19.
by zdne 11y ago
Swagger and API Blueprint are two different formats to describe web APIs. Until now Apiary and its tools supported only the API Blueprint. This has changed today.
20.
by zdne 11y ago
> far less data /author of API Blueprint here/ I would not say this is the case. API Blueprint focuses on different data for various reasons (design-first, documentation-orinented). In order to bring the Swagger support we had
21.
by zdne 11y ago
/disclaimer: I work at Apiary/ A hosted mock server is part of Apiary suite of tools for the entire API design lifecycle. Others would include interactive documentation, traffic inspector, backend testing and style guide validatio
22.
Apiary has got Swagger(blog.apiary.io)
17 points by zdne 11y ago|6 comments
23.
Think before you code (API)(blog.apiary.io)
1 points by zdne 11y ago|0 comments
24.
Tao of Good API Design(goodapi.design)
1 points by zdne 11y ago|0 comments
25.
Building smarter, more robust API clients(blog.apiary.io)
7 points by zdne 12y ago|1 comments
26.
Describing data structures in READMEs using plain text(blog.apiary.io)
12 points by zdne 12y ago|0 comments
27.
Robust API client demonstration (iOS)(vimeo.com)
1 points by zdne 12y ago|0 comments
28.
by zdne 12y ago
> TDDing an API... Yes and no. Depends how you "write" those tests. In this case, where you describe the scenarios, it is indeed true. However you can take a different approach – without writing explicit tests (and thus the cli
29.
by zdne 12y ago
Specification by example. +1
30.
by zdne 12y ago
This looks interesting! Might be worth taking a look at the library we have built to validate the HTTP messages using `curl-trace-parser` ( https://github.com/apiaryio/gavel )

More ›