#sdks — Public Fediverse posts

#Anthropic acquired #Stainless, a startup founded by former Stripe engineer Alex Rattray, for over $300 million. Stainless, backed by Sequoia Capital and Andreessen Horowitz, automates the creation and maintenance of software development kits (#SDKs) for #APIs. https://techcrunch.com/2026/05/18/anthropic-has-acquired-the-dev-tools-startup-used-by-openai-google-and-cloudflare/?eicker.news #tech #media #news

#Anthropic acquired #Stainless, a startup founded by former Stripe engineer Alex Rattray, for over $300 million. Stainless, backed by Sequoia Capital and Andreessen Horowitz, automates the creation and maintenance of software development kits (#SDKs) for #APIs. https://techcrunch.com/2026/05/18/anthropic-has-acquired-the-dev-tools-startup-used-by-openai-google-and-cloudflare/?eicker.news #tech #media #news

#Anthropic acquired #Stainless, a startup founded by former Stripe engineer Alex Rattray, for over $300 million. Stainless, backed by Sequoia Capital and Andreessen Horowitz, automates the creation and maintenance of software development kits (#SDKs) for #APIs. https://techcrunch.com/2026/05/18/anthropic-has-acquired-the-dev-tools-startup-used-by-openai-google-and-cloudflare/?eicker.news #tech #media #news

#Anthropic acquired #Stainless, a startup founded by former Stripe engineer Alex Rattray, for over $300 million. Stainless, backed by Sequoia Capital and Andreessen Horowitz, automates the creation and maintenance of software development kits (#SDKs) for #APIs. https://techcrunch.com/2026/05/18/anthropic-has-acquired-the-dev-tools-startup-used-by-openai-google-and-cloudflare/?eicker.news #tech #media #news

#Anthropic acquired #Stainless, a startup founded by former Stripe engineer Alex Rattray, for over $300 million. Stainless, backed by Sequoia Capital and Andreessen Horowitz, automates the creation and maintenance of software development kits (#SDKs) for #APIs. https://techcrunch.com/2026/05/18/anthropic-has-acquired-the-dev-tools-startup-used-by-openai-google-and-cloudflare/?eicker.news #tech #media #news

ICYMI: Google merges all ads developer tools into one hub - is it enough?: Google launched a unified Advertising and Measurement Developers Hub on April 6, covering APIs, SDKs, tagging, analytics, and publisher tools in one portal. https://ppc.land/google-merges-all-ads-developer-tools-into-one-hub-is-it-enough/ #GoogleAds #Advertising #DigitalMarketing #APIs #SDKs

🧩 SDKs should unlock real workflows, not just item reads.

With 1Password SDKs, integrations can now support:
🧰 Full vault management (CRUD + list)
🔐 User-authenticated SDK sessions
🚀 Batch actions for performance at scale

The result is a new class of integrations designed for enterprise operational workflows, where managing access matters as much as securing secrets.

👉 https://bit.ly/3Mj3QWo

#DeveloperTools #SDKs #IdentitySecurity #AccessManagement #1Password

🧩 SDKs should unlock real workflows, not just item reads.

With 1Password SDKs, integrations can now support:
🧰 Full vault management (CRUD + list)
🔐 User-authenticated SDK sessions
🚀 Batch actions for performance at scale

The result is a new class of integrations designed for enterprise operational workflows, where managing access matters as much as securing secrets.

👉 https://bit.ly/3Mj3QWo

#DeveloperTools #SDKs #IdentitySecurity #AccessManagement #1Password

🧩 SDKs should unlock real workflows, not just item reads.

With 1Password SDKs, integrations can now support:
🧰 Full vault management (CRUD + list)
🔐 User-authenticated SDK sessions
🚀 Batch actions for performance at scale

The result is a new class of integrations designed for enterprise operational workflows, where managing access matters as much as securing secrets.

👉 https://bit.ly/3Mj3QWo

#DeveloperTools #SDKs #IdentitySecurity #AccessManagement #1Password

🧩 SDKs should unlock real workflows, not just item reads.

With 1Password SDKs, integrations can now support:
🧰 Full vault management (CRUD + list)
🔐 User-authenticated SDK sessions
🚀 Batch actions for performance at scale

The result is a new class of integrations designed for enterprise operational workflows, where managing access matters as much as securing secrets.

👉 https://bit.ly/3Mj3QWo

#DeveloperTools #SDKs #IdentitySecurity #AccessManagement #1Password

🧩 SDKs should unlock real workflows, not just item reads.

With 1Password SDKs, integrations can now support:
🧰 Full vault management (CRUD + list)
🔐 User-authenticated SDK sessions
🚀 Batch actions for performance at scale

The result is a new class of integrations designed for enterprise operational workflows, where managing access matters as much as securing secrets.

👉 https://bit.ly/3Mj3QWo

#DeveloperTools #SDKs #IdentitySecurity #AccessManagement #1Password

IPIDEA Proxy Network Dismantled: Global Cybercrime and Botnet Risks Exposed https://thecyberexpress.com/ipidea-proxy-residential-network-disruption/ #TheCyberExpressNews #GooglePlayProtect #TheCyberExpress #FirewallDaily #ProxyNetwork #DarkWebNews #IPaddresses #IPIDEAproxy #CyberNews #GTIG #SDKs

IPIDEA Proxy Network Dismantled: Global Cybercrime and Botnet Risks Exposed https://thecyberexpress.com/ipidea-proxy-residential-network-disruption/ #TheCyberExpressNews #GooglePlayProtect #TheCyberExpress #FirewallDaily #ProxyNetwork #DarkWebNews #IPaddresses #IPIDEAproxy #CyberNews #GTIG #SDKs

IPIDEA Proxy Network Dismantled: Global Cybercrime and Botnet Risks Exposed https://thecyberexpress.com/ipidea-proxy-residential-network-disruption/ #TheCyberExpressNews #GooglePlayProtect #TheCyberExpress #FirewallDaily #ProxyNetwork #DarkWebNews #IPaddresses #IPIDEAproxy #CyberNews #GTIG #SDKs

IPIDEA Proxy Network Dismantled: Global Cybercrime and Botnet Risks Exposed https://thecyberexpress.com/ipidea-proxy-residential-network-disruption/ #TheCyberExpressNews #GooglePlayProtect #TheCyberExpress #FirewallDaily #ProxyNetwork #DarkWebNews #IPaddresses #IPIDEAproxy #CyberNews #GTIG #SDKs

Should I apply there?? 🤔🤔🤔🤔

https://adjoe.io/careers/open-positions/8091e129-8708-40de-851c-b83b4331af00/

> Our #AntiFraud Solutions team tackles one of #adtech’s biggest challenges: industry reports suggest 25% of global mobile ad spend is fraudulent. We’ve built sophisticated systems that actively prevent fraud from impacting our partners’ business.

> At the core of our solution are custom-built mobile #SDKs for #Android and #iOS, which analyze device integrity and detect modifications like Xposed frameworks, Magisk modules or #jailbroken devices. Our distributed cloud infrastructure powered by SQS and Kafka processes billions of daily events to flag suspicious behaviors in real time, while Go-based microservices deliver millisecond-level responses using DynamoDB as our database.

Should I apply there?? 🤔🤔🤔🤔

https://adjoe.io/careers/open-positions/8091e129-8708-40de-851c-b83b4331af00/

> Our #AntiFraud Solutions team tackles one of #adtech’s biggest challenges: industry reports suggest 25% of global mobile ad spend is fraudulent. We’ve built sophisticated systems that actively prevent fraud from impacting our partners’ business.

> At the core of our solution are custom-built mobile #SDKs for #Android and #iOS, which analyze device integrity and detect modifications like Xposed frameworks, Magisk modules or #jailbroken devices. Our distributed cloud infrastructure powered by SQS and Kafka processes billions of daily events to flag suspicious behaviors in real time, while Go-based microservices deliver millisecond-level responses using DynamoDB as our database.

Should I apply there?? 🤔🤔🤔🤔

https://adjoe.io/careers/open-positions/8091e129-8708-40de-851c-b83b4331af00/

> Our #AntiFraud Solutions team tackles one of #adtech’s biggest challenges: industry reports suggest 25% of global mobile ad spend is fraudulent. We’ve built sophisticated systems that actively prevent fraud from impacting our partners’ business.

> At the core of our solution are custom-built mobile #SDKs for #Android and #iOS, which analyze device integrity and detect modifications like Xposed frameworks, Magisk modules or #jailbroken devices. Our distributed cloud infrastructure powered by SQS and Kafka processes billions of daily events to flag suspicious behaviors in real time, while Go-based microservices deliver millisecond-level responses using DynamoDB as our database.

Should I apply there?? 🤔🤔🤔🤔

https://adjoe.io/careers/open-positions/8091e129-8708-40de-851c-b83b4331af00/

> Our #AntiFraud Solutions team tackles one of #adtech’s biggest challenges: industry reports suggest 25% of global mobile ad spend is fraudulent. We’ve built sophisticated systems that actively prevent fraud from impacting our partners’ business.

> At the core of our solution are custom-built mobile #SDKs for #Android and #iOS, which analyze device integrity and detect modifications like Xposed frameworks, Magisk modules or #jailbroken devices. Our distributed cloud infrastructure powered by SQS and Kafka processes billions of daily events to flag suspicious behaviors in real time, while Go-based microservices deliver millisecond-level responses using DynamoDB as our database.

I just recently noticed that there are not many in-depth resources about SDK documentation for technical writers. I think this presentation provides a good "no frills" overview of the topic:

"SDK docs written by developers tend to be implementer oriented, not user oriented. That makes sense, since it's the implementers writing them. Unfortunately, this approach leads to some frustrating SDK reference manual experiences for users. The implementer-oriented doc writer tends to answer, "What is this built on?" As a user, I need docs that tell me, "What can I build with this?"

I provide examples of common SDK docs pitfalls, then present the approach that I used updating the SDK documentation that our developers had created. My goal was to give users of those docs a quick, enjoyable, user-oriented experience. To do so, I identified the likely use cases, or flows, of our product. I then grouped all entities (classes, functions, etc.) of the docs into these flows. For each flow, I arranged the entities in "flow order".

Having mapped out our codebase in this way, I was ready to begin adding content by following these principles:

1) In the leading lines, answer: what is this for? 2) Always link to the previous and next items in all flows and add "See Also" links. 3) Add a code example that demonstrates this entity's role in the flow. 4) Call out gotchas that are likely to get in the user's way when trying to use a flow."

https://www.writethedocs.org/videos/portland/2019/sdk-reference-manuals-a-flow-based-approach-chris-bush/

#TechnicalWriting #SoftwareDocumentation #SDKs #SDKDocumentation

I just recently noticed that there are not many in-depth resources about SDK documentation for technical writers. I think this presentation provides a good "no frills" overview of the topic:

"SDK docs written by developers tend to be implementer oriented, not user oriented. That makes sense, since it's the implementers writing them. Unfortunately, this approach leads to some frustrating SDK reference manual experiences for users. The implementer-oriented doc writer tends to answer, "What is this built on?" As a user, I need docs that tell me, "What can I build with this?"

I provide examples of common SDK docs pitfalls, then present the approach that I used updating the SDK documentation that our developers had created. My goal was to give users of those docs a quick, enjoyable, user-oriented experience. To do so, I identified the likely use cases, or flows, of our product. I then grouped all entities (classes, functions, etc.) of the docs into these flows. For each flow, I arranged the entities in "flow order".

Having mapped out our codebase in this way, I was ready to begin adding content by following these principles:

1) In the leading lines, answer: what is this for? 2) Always link to the previous and next items in all flows and add "See Also" links. 3) Add a code example that demonstrates this entity's role in the flow. 4) Call out gotchas that are likely to get in the user's way when trying to use a flow."

https://www.writethedocs.org/videos/portland/2019/sdk-reference-manuals-a-flow-based-approach-chris-bush/

#TechnicalWriting #SoftwareDocumentation #SDKs #SDKDocumentation

I just recently noticed that there are not many in-depth resources about SDK documentation for technical writers. I think this presentation provides a good "no frills" overview of the topic:

"SDK docs written by developers tend to be implementer oriented, not user oriented. That makes sense, since it's the implementers writing them. Unfortunately, this approach leads to some frustrating SDK reference manual experiences for users. The implementer-oriented doc writer tends to answer, "What is this built on?" As a user, I need docs that tell me, "What can I build with this?"

I provide examples of common SDK docs pitfalls, then present the approach that I used updating the SDK documentation that our developers had created. My goal was to give users of those docs a quick, enjoyable, user-oriented experience. To do so, I identified the likely use cases, or flows, of our product. I then grouped all entities (classes, functions, etc.) of the docs into these flows. For each flow, I arranged the entities in "flow order".

Having mapped out our codebase in this way, I was ready to begin adding content by following these principles:

1) In the leading lines, answer: what is this for? 2) Always link to the previous and next items in all flows and add "See Also" links. 3) Add a code example that demonstrates this entity's role in the flow. 4) Call out gotchas that are likely to get in the user's way when trying to use a flow."

https://www.writethedocs.org/videos/portland/2019/sdk-reference-manuals-a-flow-based-approach-chris-bush/

#TechnicalWriting #SoftwareDocumentation #SDKs #SDKDocumentation

I just recently noticed that there are not many in-depth resources about SDK documentation for technical writers. I think this presentation provides a good "no frills" overview of the topic:

"SDK docs written by developers tend to be implementer oriented, not user oriented. That makes sense, since it's the implementers writing them. Unfortunately, this approach leads to some frustrating SDK reference manual experiences for users. The implementer-oriented doc writer tends to answer, "What is this built on?" As a user, I need docs that tell me, "What can I build with this?"

I provide examples of common SDK docs pitfalls, then present the approach that I used updating the SDK documentation that our developers had created. My goal was to give users of those docs a quick, enjoyable, user-oriented experience. To do so, I identified the likely use cases, or flows, of our product. I then grouped all entities (classes, functions, etc.) of the docs into these flows. For each flow, I arranged the entities in "flow order".

Having mapped out our codebase in this way, I was ready to begin adding content by following these principles:

1) In the leading lines, answer: what is this for? 2) Always link to the previous and next items in all flows and add "See Also" links. 3) Add a code example that demonstrates this entity's role in the flow. 4) Call out gotchas that are likely to get in the user's way when trying to use a flow."

https://www.writethedocs.org/videos/portland/2019/sdk-reference-manuals-a-flow-based-approach-chris-bush/

#TechnicalWriting #SoftwareDocumentation #SDKs #SDKDocumentation

I just recently noticed that there are not many in-depth resources about SDK documentation for technical writers. I think this presentation provides a good "no frills" overview of the topic:

"SDK docs written by developers tend to be implementer oriented, not user oriented. That makes sense, since it's the implementers writing them. Unfortunately, this approach leads to some frustrating SDK reference manual experiences for users. The implementer-oriented doc writer tends to answer, "What is this built on?" As a user, I need docs that tell me, "What can I build with this?"

I provide examples of common SDK docs pitfalls, then present the approach that I used updating the SDK documentation that our developers had created. My goal was to give users of those docs a quick, enjoyable, user-oriented experience. To do so, I identified the likely use cases, or flows, of our product. I then grouped all entities (classes, functions, etc.) of the docs into these flows. For each flow, I arranged the entities in "flow order".

Having mapped out our codebase in this way, I was ready to begin adding content by following these principles:

1) In the leading lines, answer: what is this for? 2) Always link to the previous and next items in all flows and add "See Also" links. 3) Add a code example that demonstrates this entity's role in the flow. 4) Call out gotchas that are likely to get in the user's way when trying to use a flow."

https://www.writethedocs.org/videos/portland/2019/sdk-reference-manuals-a-flow-based-approach-chris-bush/

#TechnicalWriting #SoftwareDocumentation #SDKs #SDKDocumentation

🎉 Breaking news: #Postgres has a "LISTEN/NOTIFY" feature that didn't quite make it as the life of the party! 🎈NewRecall.ai discovers that it doesn’t "scale," a shocking revelation akin to discovering water is wet 💧. Just another day in the thrilling world of #desktop #SDKs and #meeting #bots. 💤
https://www.recall.ai/blog/postgres-listen-notify-does-not-scale #LISTEN #NOTIFY #NewRecall #AI #scaling #issues #HackerNews #ngated

🤔 Ah, behold the 'MCP Specification,' a sprawling labyrinth of buzzwords and acronyms promising to revolutionize the world with yet another "open protocol" nobody asked for. 🚀 Did someone say "standardized way"? Because obviously, the tech world hasn't seen enough of those. 🙄 Expect all the excitement of a tax code, but with SDKs!
https://modelcontextprotocol.io/specification/2025-06-18 #MCPSpecification #openprotocol #techbuzzwords #SDKs #standardization #HackerNews #ngated

What does the board need to know about mobile #privacy & #compliance?

Find out at #NSConnect25 with Andrew Hoog of NowSecure and Steven Roosa of Norton Rose Fulbright. Apps, OTT, #SDKs — all under scrutiny.

Register here: https://events.bizzabo.com/nowsecure-connect-2025/agenda/session/1628652?utm_source=mastodon&utm_medium=organic&utm_campaign=connect25&utm_content=june13

AI code + open source + #SDKs = rising AppSec risk. ⚠️

At #NSConnect25, Vishrut Iyengar of Black Duck & Brian Murphy of #NowSecure show how TrueScale + mobile testing give full coverage - without slowing dev. Register: https://events.bizzabo.com/nowsecure-connect-2025/agenda/session/1628644?utm_source=mastodon&utm_medium=organic&utm_campaign=connect25&utm_content=June6

🚀 Behold: a "revolutionary" Bash script heroically squeezing an SDK into 250 lines. Because, clearly, who needs robust languages when you can wrangle server logic with the elegance of a raccoon in a trash can? 🎩✨
https://github.com/muthuishere/mcp-server-bash-sdk #BashScript #SDKs #CodingHumor #DevLife #TechInnovation #HackerNews #ngated

TOMORROW #Esri Devs webinar, What's New: #Developer Experience (Sept 2023) - Fri Sept 15, 9 am PST http://esri.social/T6VC50PKPmZ

#developers #geodev #esridev #esrijs #webapps #mapping #maps #GIS #SDKs #native #esri #arcgis #GISchat #geospatial #mapstodon

#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

20M JavaScript devs can now build applications on NEAR: KBW 2022

https://cointelegraph.com/news/20m-javascript-devs-can-now-build-applications-on-near-kbw-2022

#Blockchainsmartcontracts #SoftwareDevelopmentKit #NEARProtocol #JavaScript #SDKs

🔗 Efficient integration: Compatible with existing #REST #API and supports #OpenAI and #Anthropic #SDKs
🆓 Free public beta phase available until June 5, 2025 for testing and exploration
📚 Comprehensive documentation and developer guides provided

Nieuwe versie developer.overheid.nl live

De vernieuwde developer.overheid.nl is live. Dit platform helpt ontwikkelaars binnen de overheid om efficiënter te werken met digitale tools, standaarden en API’s (Application Programming Interface). De update maakt het portaal toegankelijker en gebruiksvriendelijker. Overheidsorganisaties kunnen hier eenvoudiger samenwerken en bestaande oplossingen hergebruiken.

Veel overheden ontwikkelen namelijk vergelijkbare digitale diensten, zoals formulieren voor vergunningaanvragen of inlogsystemen. Op developer.overheid.nl staan hergebruik en innovatie centraal. Ontwikkelaars vinden nu makkelijker kant-en-klare API’s en SDK’s (Software Development Kit) om deze diensten sneller en veiliger te bouwen. Dit voorkomt dubbel werk en bespaart tijd en kosten.

Nieuwe kennisbank met praktijkvoorbeelden

Een belangrijke toevoeging is de kennisbank, waarin standaarden, tools en best practices worden gebundeld. Denk aan richtlijnen voor het veilig gebruiken van open source of voorbeelden van succesvolle samenwerkingen, zoals de herbruikbare open source code voor gemeentelijke websiteformulieren.

Community en samenwerking

Het platform stimuleert samenwerking tussen overheidsontwikkelaars. Teams kunnen ervaringen delen, elkaar helpen bij technische uitdagingen en samen nieuwe toepassingen ontwikkelen. Zo profiteren alle overheidsorganisaties van elkaars kennis en oplossingen.

Meer informatie

Lees het volledige nieuwsbericht op developer.overheid.nl.

Dit is een automatisch geplaatst bericht. Vragen of opmerkingen kun je richten aan @[email protected]

#apiS #data #digitaleTools #digitalisering #Kennisbank #nieuwsbrief72025 #openSource #SDKS

"SDK generators are revolutionizing the way developers approach API integrations. These powerful tools automate the creation of software development kits (SDKs), eliminating the repetitive and time-consuming task of writing boilerplate code. By doing so, they enable developers to focus on building features and solving real-world problems rather than dealing with the complexities of manual SDK creation.

In this post, we’ll take a deep dive into SDK generators — what they are, how they work, and the key features that make them indispensable in modern software development. We’ll also discuss their numerous benefits, from accelerating project timelines to reducing errors, and how they contribute to a more seamless developer experience. Whether you’re a solo developer or part of a large team, SDK generators can help you save time, enhance efficiency, and deliver better products faster.

Let’s explore why SDK generators are game-changers and how they’re transforming the way we build and integrate APIs."

https://nordicapis.com/review-of-8-sdk-generators-for-apis-in-2025/

#APIs #SDKs #SDKGenerators #Programming #SoftwareDevelopment

Craft dynamic entity data sources for #ArcGIS #MAPS #SDKs for Native #Apps https://tinyurl.com/3p5zt5nj

#developers #geodev #esridev #Runtime #dataviz #GIS #esri #mapping #geospatial #GISchat #mapstodon

This article explores 𝐰𝐡𝐚𝐭 𝐒𝐃𝐊𝐬 𝐚𝐧𝐝 𝐀𝐏𝐈𝐬 𝐀𝐮𝐭𝐡𝐠𝐞𝐚𝐫 offers and how they can 𝐬𝐢𝐦𝐩𝐥𝐢𝐟𝐲 𝐚𝐮𝐭𝐡𝐞𝐧𝐭𝐢𝐜𝐚𝐭𝐢𝐨𝐧 𝐢𝐧𝐭𝐞𝐠𝐫𝐚𝐭𝐢𝐨𝐧 for developers.

https://authgear.com/post/simplifying-authentication-integration-with-authgear-sdks

#security #authentication #authgear #sdks #developertools

Fern is an #opensource format for defining #REST #APIs. You can think of it like a programming language to describe your #API: your endpoints, types, errors, and examples.

Generate #SDKs (client libraries) for your API

https://github.com/fern-api/fern

8 essential #realtime techniques with #ArcGIS #Maps #SDKs for Native #Apps https://tinyurl.com/bdhfbvyb

#developers #geodev #esridev #Runtime #dataviz #GIS #esri #mapping #geospatial #esridevs #mapstodon

I'm torn on the value of generic libraries - e.g. a #Go testing library. While I dislike repetitive code, the abstractions API is never complete, and deps mgmt can often be too involved.

Often I found internal company #SDKs to be more powerful. Curious to hear what others think.

@WuMargaret @Perl @yarmo The #OpenFoodFacts #API, #SDKs, and their database of over 2.8 million products are also available to anyone under very permissive terms: https://openfoodfacts.org/data

And they dogfood (haha) the API with their mobile apps, so you know it’s maintained.

#food #nutrition

#ICYMInfoQ
👇 A collection of the best #dotnet articles published on #InfoQ in 2022!

1 ✅ Creating and Using HTTP Client SDKs in .NET 6: http://bit.ly/3HgXKQR
Get insights into the process behind developing #HTTP Client #SDKs in #dotnet 6! Oleksii Nikiforov shares a sample SDK explained in detail, with considerations for different scenarios.

2 ✅ InfoQ .NET Trends Report 2022: http://bit.ly/3D1nhuS
InfoQ presents a general analysis of the current status of the #dotnet space💡.

3 ✅ Building Neural Networks with TensorFlow.NET: http://bit.ly/3Hhqglu
Read the article by Robert Krzaczyński and learn how to use TensorFlow.NET to build a neural network!:
#dotnet #TensorFlow #DeepLearning #MachineLearning

Inspired by this amazing content? If you are a software professional passionate about innovation join our team of .NET contributors! Share actionable ideas in writing and become more visible in the software community! Find out more and get in touch: https://bit.ly/3R7y9vC

List of #FOSS #Games, Game #Engines and #SDKs on #GitHub

List
https://github.com/michelpereira/games

Zoom launches $100M Zoom Apps investment fund - When Zoom launched Zoom Apps and the Marketplace as a place to sell them last year... - http://feedproxy.google.com/~r/Techcrunch/~3/DNTZ2BKZbzY/ #corporateinvestmentarms #videoconferencing #developer #startups #cloud #apis #sdks #zoom #tc

TOMORROW #Esri Devs webinar, What's New: #Developer Experience (Sept 2023) - Fri Sept 15, 9 am PST http://esri.social/T6VC50PKPmZ

#developers #geodev #esridev #esrijs #webapps #mapping #maps #GIS #SDKs #native #esri #arcgis #GISchat #geospatial #mapstodon

TOMORROW #Esri Devs webinar, What's New: #Developer Experience (Sept 2023) - Fri Sept 15, 9 am PST http://esri.social/T6VC50PKPmZ

#developers #geodev #esridev #esrijs #webapps #mapping #maps #GIS #SDKs #native #esri #arcgis #GISchat #geospatial #mapstodon

TOMORROW #Esri Devs webinar, What's New: #Developer Experience (Sept 2023) - Fri Sept 15, 9 am PST http://esri.social/T6VC50PKPmZ

#developers #geodev #esridev #esrijs #webapps #mapping #maps #GIS #SDKs #native #esri #arcgis #GISchat #geospatial #mapstodon

TOMORROW #Esri Devs webinar, What's New: #Developer Experience (Sept 2023) - Fri Sept 15, 9 am PST http://esri.social/T6VC50PKPmZ

#developers #geodev #esridev #esrijs #webapps #mapping #maps #GIS #SDKs #native #esri #arcgis #GISchat #geospatial #mapstodon