florianmartens

5 ms·

1.
by florianmartens 1y ago
Nice. This is interesting and maybe I can connect this with pipe0.com to add emails, phone numbers, etc.
2.
by florianmartens 1y ago
The value of clay is is not its code base IMO. Clay connects many providers that each have licenses starting around $100-150/mo. Even if you open source your solution, users would still have to purchase subscriptions individually, mana
3.
How I Use Remind(1)(blog.thechases.com)
2 points by florianmartens 1y ago|0 comments
4.
Show HN: Pipe0 a data enrichment framework for next-gen sales technology(pipe0.com)
1 points by florianmartens 1y ago|0 comments
5.
by florianmartens 2y ago
Thanks for posting this. I'm building https://api-fiddle.com and need to have this on the map as a potential default format for the editor.
6.
by florianmartens 2y ago
Try api-fiddle.com as a replacement for stoplight.io :)
7.
by florianmartens 2y ago
I've bookmarked your blog and will follow along to see what kind of solution you come up with in the end :)
8.
by florianmartens 2y ago
Yeah, I think even if you are fairly technical it's still pretty hard to manage a growing OpenAPI doc that is good enough to generate clients, sdks and docs from it. I think that we'll soon be able to help you generate mock client
9.
by florianmartens 2y ago
That's really cool. We're on a similar path with https://api-fiddle.com We're trying to build the best tool out there for team that want to build api-first and speed up development and code generation this way. I&
10.
by florianmartens 2y ago
I think this is a good intro into OpenAPI contracts. What generally sells people into OpenAPI is: 1.) The ability to document things with tools like swagger ui, api-fiddle, scalar 2.) The ability to automate things with auto-generated api-c
11.
by florianmartens 2y ago
I agree. API-first is the way! Change your schema, auto-generate types into your code and use them for your server definition. It's just faster and more secure this way. Use api-fiddle.com or spotlight.io to work with the schemas (bran
12.
by florianmartens 2y ago
This article is awesome and resonates with my experience! I used to work for one of the big cloud vendors. We frequently had doc writers in our sync calls. Quite frankly, they never had a chance! Much of our documentation, our errors, statu
13.
Why Generating OpenAPI Specifications from Code Is a Bad Idea(blog.api-fiddle.com)
2 points by florianmartens 2y ago|0 comments
14.
by florianmartens 2y ago
Dieter Rams’ design philosophy encourages simplicity, honesty, and functionality—values that translate beautifully into the world of API design. By applying these 10 principles to REST APIs, developers can create APIs that are not only func
15.
Dieter Rams' 10 Principles of Good Design Can Shape REST API Design(blog.api-fiddle.com)
1 points by florianmartens 2y ago|1 comments
16.
What's the Difference Between Console, Terminal, Emulators, and Shell Anyway?(blog.api-fiddle.com)
3 points by florianmartens 2y ago|1 comments
17.
by florianmartens 2y ago
Hopefully the last blog post you ever have to read on the matter
18.
Coolify’s rise to fame, and why it could be a big deal(blog.api-fiddle.com)
172 points by florianmartens 2y ago|62 comments
19.
by florianmartens 7y ago
I'd definitely declutter the index page. It's literally too (ooo...) much text. Maybe clarify your value proposition.
20.
by florianmartens 7y ago
Hm, I'd also argue that accountability would help. Create it somehow find a partner with whom you work out. Document you workout in a blog, youtube, whatsapp conversation, conversation on Eightygram. Or, ignoring technology. Find a per