#specfirst — Public Fediverse posts

"AI-driven security and spec-first IDEs are revolutionizing software development. Tools like Defender for Cloud and GitHub Advanced Security offer runtime insights, while spec-first tools like Kiro and Spec Kit embed security into code from the start. Faster remediation, better security, and a shift from code-first to intent-first development. #AIInnovation #DevSecOps #SpecFirst #CodeSecurity #SoftwareEngineering"

https://saysomething.hashnode.dev/ai-driven-security-spec-first-development-reshaping-secure-software

🚧 Done with midnight patch-ups? See how a one-page spec + Kiro’s agents cut bugs by 47 %. 👩‍💻💡 Read now → https://medium.com/@rogt.x1997/from-vibes-to-version-control-how-amazons-kiro-turns-ai-coding-sparks-into-shipping-software-bc97d2c6227d #AIcoding #SpecFirst #DevWorkflow
https://medium.com/@rogt.x1997/from-vibes-to-version-control-how-amazons-kiro-turns-ai-coding-sparks-into-shipping-software-bc97d2c6227d

I've finally got to publish the fourth API newsletter: https://www.bitoff.org/the-api-dispatch-4/

The topic is Language-Oriented Approach to API Development from @smizell, something more developers should know about.

#TheApiDispatch #SpecFirst #TypeSpec #smithy

"Moonwalk – 2025 update"
https://www.openapis.org/blog/2025/02/05/moonwalk-2025-update

#openapi #Moonwalk #APIfirst #specfirst

I am working on adding "coverage" to the openapi_first rubygem.

This can be used to see if you have tested all requests/responses in your OpenAPI API description.

Please check it out. Any feedback on this would be greatly appreciated: https://github.com/ahx/openapi_first/tree/coverage?tab=readme-ov-file#test-coverage

#openapi #specfirst #apifirst #ruby #rack

"In short, APIs are how businesses speak to one another. Breaking this oath with a poor integration experience is a surefire way to reduce your business potential. By utilizing a source of truth and baking a specification-first approach into your API development and documentation practices, you more clearly communicate changes, reducing the possibility of broken clients and promoting forward compatibility. Great API products must be well-described, easy to understand, and predictable in the long run.

In the end, the business effects of specification-driven development are manifold. Whether you're building RESTful, GraphQL, or event-driven partner services, having reliable API documentation is important to compete in the digital economy. This consistency equates to a better partner experience, leading to stickier partners and less customer churn. By enabling smoother integrations and reducing frustration, spec-first documentation directly contributes to partner retention and loyalty, which ultimately drives revenue growth."

https://bump.sh/blog/how-spec-first-api-documentation-aids-partner-integration

#APIs #APIDocumentation #TechnicalWriting #SpecFirst #SoftwareDocumentation #Docs #DeveloperExperience #DocsAsCode

Fellow #golang people, how do you generate Go client and server skeletons from #OpenAPI specs in your projects?

I’m currently using https://github.com/oapi-codegen/oapi-codegen but I’m eager to learn about alternatives.

I also know https://github.com/OpenAPITools/openapi-generator.

#SpecFirst #SpecDriven

Navigating OpenAPI, TypeSpec, and API-Drift in the "Post-OpenAPI Era"

https://netapinotes.com/navigating-openapi-typespec-and-api-drift-in-the-post-openapi-era/

"In a perfect world as an API program lead, I would like to see a run-time comparison, per request, between what the API is doing and what it purports to do." -- #MatthewReinbold

#api360 #APIFirst #specFirst #typeSpec