Joined November 2012
- Tweets 422
- Following 445
- Followers 182
- Likes 239
43 Photos and videos
10 Oct 2024
For any Wordle fans out there, I created a similar daily puzzle...
Find the number sequence in as few guesses as possible
producthunt.com/posts/sequenβ¦
1
138
4 Oct 2023
I'm so excited to attend #apidays Australia next week as a speaker!
My topic is "Mapping your business model to API design". Whether you're a tech person or from business, there will be something in it for you!
Register here --> ticket.apidays.global/event/β¦
4
184
James Moschou retweeted
29 Aug 2023
Date and time information is so common in APIs that they can make or break your API's developer experience - evaluate different approaches based on your use case from @getcriteria
hubs.li/Q01ZxpXF0
3
2
462
James Moschou retweeted
7 Aug 2023
Friend of mine @jcmosc has built a really cool tool for building flow diagrams that integrate with your OpenAPI spec π
Take a look at diagrams.criteria.sh/
ALT A screenshot of Criteria diagrams showing an authorization flow between the user, a web application, and an authorization server.
1
1
163
1 Aug 2023
I've been a bit quiet on here, bootstrapping a collaborative design platform is definitely not easy...
So I'm going to pivot away from collaboration and release some mini products where folks can get value in seconds, starting with...
Criteria Diagrams
diagrams.criteria.sh/
2
1
89
1 Aug 2023
Because the focus is on API workflows, you can import an OpenAPI file and autogenerate flows much more rapidly than general-purpose tools allow.
Since diagrams are intended to be published in public docs, they have a much more polished and professional appearance.
1
58
1 Aug 2023
Try it out and let me know what you think! (And watch this space)
49
James Moschou retweeted
4 Jun 2023
πππ
Here's a quick roundup of what we released this May:
1. Sync Spectral rulesets
2. Configure API styles
3. Import Swagger 2.0 documents
Keep reading on...
1
1
111
24 May 2023
Been thinking about the future role of AI automation in APIs.
I think we're gonna see AI write code on the consumer side first. The provider side of API development is still very much led by humans.
1
1
93
24 May 2023
3. AIs are excellent writing boilerplate code.
This makes AIs great at writing API clients and "glue" code.
Zapier says it takes about 2 weeks for a tool to integrate into their platform. An AI-powered Zapier could onboard any tool immediately.
1
1
52
24 May 2023
Soon a large proportion of your API's consumers will not be developers, but AIs.
We'll be writings docs, not for developers, but for language models.
Maybe it's time to start using #aiexperience instead of #developerexperience?
1
47
22 May 2023
I'm looking back at my old notes from customer conversations and I've got the digital equivalent of "can't read my own handwriting".
What automated transcription tools do people like that work with Google Meet?
#indiehackers
2
89
21 May 2023
Thinking about writing about how to migrate an API platform from a code-first approach to an API-first/docs-as-code workflow. Based on experience.
Would this be useful to folks?
1
65
15 May 2023
That feeling when you notice new signups to your startup π
Then you notice they're from your main competitor π¬
2
5
114
17 May 2023
To be completely fair, I created an account in their product first, for research (and legitimate use at prior jobs).
But the feeling that a company with 50x resources might swoop in and obsolete you is kinda nervewracking.
44
James Moschou retweeted
8 May 2023
In case you missed it, April saw the release of two new features:
1. π¦ Shared Components
2. π― Team Workspaces
Here's a quick summary:
1
1
2
93
17 Apr 2023
How do I convince every developer in the world that their email field should actually be named email_address? Because an email is the actual thing being sent, not where it's sent to.
3
76