#developerdocumentation — Public Fediverse posts

"The reality is that documentation is no longer just a piece of context or data found when an external developer runs into an issue — it’s a first-class context object that needs to be treated with the same focus and intentionality as the API itself. Within this context, MCP offers something more than just putting all the documentation in a single store and hoping for the best — it provides a direct pathway between the developer and the provider, allowing you to discover intent, and clarity like no other process currently on offer.

As we move towards a future focused around API discovery, we need to rethink how we look at documentation and its discovery — and solutions like MCP are going to play a huge part in making documentation and data clearer, more contextual, and more available."

https://nordicapis.com/using-mcp-for-api-documentation-discovery/

#AI #GenerativeAI #AIAgents #AgenticAI #MCP #MCPServers #Documentation #APIDocumentation #SoftwareDocumentation #DeveloperDocumentation #APIs #APIDiscovery

"The reality is that documentation is no longer just a piece of context or data found when an external developer runs into an issue — it’s a first-class context object that needs to be treated with the same focus and intentionality as the API itself. Within this context, MCP offers something more than just putting all the documentation in a single store and hoping for the best — it provides a direct pathway between the developer and the provider, allowing you to discover intent, and clarity like no other process currently on offer.

As we move towards a future focused around API discovery, we need to rethink how we look at documentation and its discovery — and solutions like MCP are going to play a huge part in making documentation and data clearer, more contextual, and more available."

https://nordicapis.com/using-mcp-for-api-documentation-discovery/

#AI #GenerativeAI #AIAgents #AgenticAI #MCP #MCPServers #Documentation #APIDocumentation #SoftwareDocumentation #DeveloperDocumentation #APIs #APIDiscovery

"The reality is that documentation is no longer just a piece of context or data found when an external developer runs into an issue — it’s a first-class context object that needs to be treated with the same focus and intentionality as the API itself. Within this context, MCP offers something more than just putting all the documentation in a single store and hoping for the best — it provides a direct pathway between the developer and the provider, allowing you to discover intent, and clarity like no other process currently on offer.

As we move towards a future focused around API discovery, we need to rethink how we look at documentation and its discovery — and solutions like MCP are going to play a huge part in making documentation and data clearer, more contextual, and more available."

https://nordicapis.com/using-mcp-for-api-documentation-discovery/

#AI #GenerativeAI #AIAgents #AgenticAI #MCP #MCPServers #Documentation #APIDocumentation #SoftwareDocumentation #DeveloperDocumentation #APIs #APIDiscovery

"The reality is that documentation is no longer just a piece of context or data found when an external developer runs into an issue — it’s a first-class context object that needs to be treated with the same focus and intentionality as the API itself. Within this context, MCP offers something more than just putting all the documentation in a single store and hoping for the best — it provides a direct pathway between the developer and the provider, allowing you to discover intent, and clarity like no other process currently on offer.

As we move towards a future focused around API discovery, we need to rethink how we look at documentation and its discovery — and solutions like MCP are going to play a huge part in making documentation and data clearer, more contextual, and more available."

https://nordicapis.com/using-mcp-for-api-documentation-discovery/

#AI #GenerativeAI #AIAgents #AgenticAI #MCP #MCPServers #Documentation #APIDocumentation #SoftwareDocumentation #DeveloperDocumentation #APIs #APIDiscovery

"The reality is that documentation is no longer just a piece of context or data found when an external developer runs into an issue — it’s a first-class context object that needs to be treated with the same focus and intentionality as the API itself. Within this context, MCP offers something more than just putting all the documentation in a single store and hoping for the best — it provides a direct pathway between the developer and the provider, allowing you to discover intent, and clarity like no other process currently on offer.

As we move towards a future focused around API discovery, we need to rethink how we look at documentation and its discovery — and solutions like MCP are going to play a huge part in making documentation and data clearer, more contextual, and more available."

https://nordicapis.com/using-mcp-for-api-documentation-discovery/

#AI #GenerativeAI #AIAgents #AgenticAI #MCP #MCPServers #Documentation #APIDocumentation #SoftwareDocumentation #DeveloperDocumentation #APIs #APIDiscovery

Whether you’re just getting started or looking to improve your audit process, you’ll learn how to write an effective audit report without the struggles I faced. https://hackernoon.com/how-to-audit-developer-docs-a-quick-effective-method #developerdocumentation

Whether you’re just getting started or looking to improve your audit process, you’ll learn how to write an effective audit report without the struggles I faced. https://hackernoon.com/how-to-audit-developer-docs-a-quick-effective-method #developerdocumentation

Whether you’re just getting started or looking to improve your audit process, you’ll learn how to write an effective audit report without the struggles I faced. https://hackernoon.com/how-to-audit-developer-docs-a-quick-effective-method #developerdocumentation

Whether you’re just getting started or looking to improve your audit process, you’ll learn how to write an effective audit report without the struggles I faced. https://hackernoon.com/how-to-audit-developer-docs-a-quick-effective-method #developerdocumentation

Whether you’re just getting started or looking to improve your audit process, you’ll learn how to write an effective audit report without the struggles I faced. https://hackernoon.com/how-to-audit-developer-docs-a-quick-effective-method #developerdocumentation

#DX #SDKs #DeveloperDocumentation #SoftwareDocumentation #APIs #APIDocumentation #TechnicalWriting: "Why are SDKs so important to ensuring your product is tuned for developers?

It all comes down to helping your API consumers integrate faster. When people decide to integrate with your API, they have a job they want to get done. They think your API could be the fastest path to solving it. But too often, building an integration with the API is as painful (or even more painful) as the original job. That’s counterproductive, to put it mildly. There are a hundred things your users would rather be doing than reading your API docs and writing basic integration code. The less you require of them, the happier they’ll be. And SDKs are the best tool for making sure your API remains unobtrusive.

The definition of an SDK is straightforward: It’s a library that surrounds your API and handles the boring parts of the integrating process, such as:

- Constructing an HTTP request
- Managing an authentication token
- Handling retries
- Parsing paginated responses

More powerful SDKs will go beyond request and response-handling basics and provide type safety and hinting in the integrated development environment (IDE). This means users don’t have to open a docs page; they’ll get all the information and feedback they need directly in their coding environment. It doesn’t get more efficient than that."

https://thenewstack.io/api-builders-must-sell-to-developers-or-die-slowly

#DX #SDKs #DeveloperDocumentation #SoftwareDocumentation #APIs #APIDocumentation #TechnicalWriting: "Why are SDKs so important to ensuring your product is tuned for developers?

It all comes down to helping your API consumers integrate faster. When people decide to integrate with your API, they have a job they want to get done. They think your API could be the fastest path to solving it. But too often, building an integration with the API is as painful (or even more painful) as the original job. That’s counterproductive, to put it mildly. There are a hundred things your users would rather be doing than reading your API docs and writing basic integration code. The less you require of them, the happier they’ll be. And SDKs are the best tool for making sure your API remains unobtrusive.

The definition of an SDK is straightforward: It’s a library that surrounds your API and handles the boring parts of the integrating process, such as:

- Constructing an HTTP request
- Managing an authentication token
- Handling retries
- Parsing paginated responses

More powerful SDKs will go beyond request and response-handling basics and provide type safety and hinting in the integrated development environment (IDE). This means users don’t have to open a docs page; they’ll get all the information and feedback they need directly in their coding environment. It doesn’t get more efficient than that."

https://thenewstack.io/api-builders-must-sell-to-developers-or-die-slowly

#DX #SDKs #DeveloperDocumentation #SoftwareDocumentation #APIs #APIDocumentation #TechnicalWriting: "Why are SDKs so important to ensuring your product is tuned for developers?

It all comes down to helping your API consumers integrate faster. When people decide to integrate with your API, they have a job they want to get done. They think your API could be the fastest path to solving it. But too often, building an integration with the API is as painful (or even more painful) as the original job. That’s counterproductive, to put it mildly. There are a hundred things your users would rather be doing than reading your API docs and writing basic integration code. The less you require of them, the happier they’ll be. And SDKs are the best tool for making sure your API remains unobtrusive.

The definition of an SDK is straightforward: It’s a library that surrounds your API and handles the boring parts of the integrating process, such as:

- Constructing an HTTP request
- Managing an authentication token
- Handling retries
- Parsing paginated responses

More powerful SDKs will go beyond request and response-handling basics and provide type safety and hinting in the integrated development environment (IDE). This means users don’t have to open a docs page; they’ll get all the information and feedback they need directly in their coding environment. It doesn’t get more efficient than that."

https://thenewstack.io/api-builders-must-sell-to-developers-or-die-slowly

#DX #SDKs #DeveloperDocumentation #SoftwareDocumentation #APIs #APIDocumentation #TechnicalWriting: "Why are SDKs so important to ensuring your product is tuned for developers?

It all comes down to helping your API consumers integrate faster. When people decide to integrate with your API, they have a job they want to get done. They think your API could be the fastest path to solving it. But too often, building an integration with the API is as painful (or even more painful) as the original job. That’s counterproductive, to put it mildly. There are a hundred things your users would rather be doing than reading your API docs and writing basic integration code. The less you require of them, the happier they’ll be. And SDKs are the best tool for making sure your API remains unobtrusive.

The definition of an SDK is straightforward: It’s a library that surrounds your API and handles the boring parts of the integrating process, such as:

- Constructing an HTTP request
- Managing an authentication token
- Handling retries
- Parsing paginated responses

More powerful SDKs will go beyond request and response-handling basics and provide type safety and hinting in the integrated development environment (IDE). This means users don’t have to open a docs page; they’ll get all the information and feedback they need directly in their coding environment. It doesn’t get more efficient than that."

https://thenewstack.io/api-builders-must-sell-to-developers-or-die-slowly

#DX #SDKs #DeveloperDocumentation #SoftwareDocumentation #APIs #APIDocumentation #TechnicalWriting: "Why are SDKs so important to ensuring your product is tuned for developers?

It all comes down to helping your API consumers integrate faster. When people decide to integrate with your API, they have a job they want to get done. They think your API could be the fastest path to solving it. But too often, building an integration with the API is as painful (or even more painful) as the original job. That’s counterproductive, to put it mildly. There are a hundred things your users would rather be doing than reading your API docs and writing basic integration code. The less you require of them, the happier they’ll be. And SDKs are the best tool for making sure your API remains unobtrusive.

The definition of an SDK is straightforward: It’s a library that surrounds your API and handles the boring parts of the integrating process, such as:

- Constructing an HTTP request
- Managing an authentication token
- Handling retries
- Parsing paginated responses

More powerful SDKs will go beyond request and response-handling basics and provide type safety and hinting in the integrated development environment (IDE). This means users don’t have to open a docs page; they’ll get all the information and feedback they need directly in their coding environment. It doesn’t get more efficient than that."

https://thenewstack.io/api-builders-must-sell-to-developers-or-die-slowly

Developers – dreading the idea of documentation? Shaw Innes covers code-first documentation strategies, Architecture Decision Records, the C4 Model and more to help you create light-weight and easy-to-maintain documentation so you can minimise developer onboarding times your projects.

Get your tickets now! https://www.dddmelbourne.com/tickets

#DDDMelb #developerdocumentation #documentationascode

Developers – dreading the idea of documentation? Shaw Innes covers code-first documentation strategies, Architecture Decision Records, the C4 Model and more to help you create light-weight and easy-to-maintain documentation so you can minimise developer onboarding times your projects.

Get your tickets now! https://www.dddmelbourne.com/tickets

#DDDMelb #developerdocumentation #documentationascode

Developers – dreading the idea of documentation? Shaw Innes covers code-first documentation strategies, Architecture Decision Records, the C4 Model and more to help you create light-weight and easy-to-maintain documentation so you can minimise developer onboarding times your projects.

Get your tickets now! https://www.dddmelbourne.com/tickets

#DDDMelb #developerdocumentation #documentationascode

Developers – dreading the idea of documentation? Shaw Innes covers code-first documentation strategies, Architecture Decision Records, the C4 Model and more to help you create light-weight and easy-to-maintain documentation so you can minimise developer onboarding times your projects.

Get your tickets now! https://www.dddmelbourne.com/tickets

#DDDMelb #developerdocumentation #documentationascode

Developers – dreading the idea of documentation? Shaw Innes covers code-first documentation strategies, Architecture Decision Records, the C4 Model and more to help you create light-weight and easy-to-maintain documentation so you can minimise developer onboarding times your projects.

Get your tickets now! https://www.dddmelbourne.com/tickets

#DDDMelb #developerdocumentation #documentationascode

SaaS companies can grow to $20M+ ARR by selling exclusively to developers - Sam Richard
Contributor

Share on Twitter
... - http://feedproxy.google.com/~r/Techcrunch/~3/QXGYiqpvNYQ/ #ecenterpriseapplications #developerdocumentation #developerrelations #enterprise #jefflawson #developer #eccolumn #cypress #column #github #twilio #saas #snyk