We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The text was updated successfully, but these errors were encountered:
由於這個專案應會採取前後端分離架構,個人認為可以導入 API First 的思維,將 API 作為合約介面進行設計驗證
API first 即 Contract first —— Ruddy Lee
Sorry, something went wrong.
由於這個專案應會採取前後端分離架構,個人認為可以導入 API First 的思維,將 API 作為合約介面進行設計驗證 API first 即 Contract first —— Ruddy Lee 淺談 API First – Ruddy Lee 分享空間 (wordpress.com) DevOps 潮流下的 API First 開發策略 - YouTube DevOpsDaysTaipei2022-Andrew, DevOps 潮流下的 API First 開發策略 (release) - Google 簡報 DevOps 潮流下的 API First 開發策略 - Andrew Wu - HackMD
淺談 API First – Ruddy Lee 分享空間 (wordpress.com)
DevOps 潮流下的 API First 開發策略 - YouTube
是的,我也只會這個,或者說從我帶專案開始就是 API 先行了
No branches or pull requests
The text was updated successfully, but these errors were encountered: