ADRを運用して3年経った僕らの現在地2024-10-05 YAPC::Hakodate 2024 https://yapcjapan.org/2024hakodate/
How HashiCorp Works
This article contains internal linksLearn about the How HashiCorp Works project and why there are links to internal HashiCorp materials in this article. Our writing roots date back to the company’s earliest days, when the entire team was just the co-founders, Mitchell Hashimoto and Armon Dadgar, working out of Armon’s living room. Back then, it was pretty easy to keep the company aligned. But Mitc
Docs for Developers
Overview Authors: Jared Bhatti 0, Sarah Corleissen 1, Jen Lambourne 2, David Nunez 3, … Heidi Waterhouse 4 Show authors Jared Bhatti Berkeley, USA
システムの変化に追従可能でかつ理解し易いドキュメントシステムのモデル化 / Web System Architecture #8
https://github.com/k1LoW/wsa-sg-8th-draft
Why SRE Documents Matter - ACM Queue
October 4, 2018 Volume 16, issue 4 PDF Why SRE Documents Matter How documentation enables SRE teams to manage new and existing services Shylaja Nukala and Vivek Rau SRE (site reliability engineering) is a job function, a mindset, and a set of engineering approaches for making web products and services run reliably. SREs operate at the intersection of software development and systems engineering to
Simpler GitHub Pages publishing
AI & MLLearn about artificial intelligence and machine learning across the GitHub ecosystem and the wider industry. Generative AILearn how to build with generative AI. GitHub CopilotChange how you work with GitHub Copilot. LLMsEverything developers need to know about LLMs. Machine learningMachine learning tips, tricks, and best practices. How AI code generation worksExplore the capabilities and be
Documentation
Ask questions, find answers and collaborate at work with Stack Overflow for Teams. Explore Teams Collectives™ on Stack Overflow Find centralized, trusted content and collaborate around the technologies you use most. Learn more about Collectives We have shut down Stack Overflow Documentation. Documentation was our attempt at improving existing reference materials by focusing on examples. The beta r
設定の仕様をドキュメントに書くのではなく、テストにしてしまう - $shibayu36->blog;
以前開発のドキュメントをどこに置くか問題 - $shibayu36->blog;という記事を書いた。まだよい方法はちゃんと考えられてないが、少しずつケースバイケースでいろいろな手法を試してみている。今回は設定項目の仕様のドキュメントという観点で考えたときに、テストを作ることで解決できないか、ということについて書く。 設定項目の仕様 例えば以下の様な設定があったとする*1。 [ { "blog_url" : "http://shibayu36.hatenablog.com/", "permission" : "public", "can_be_edited_by" : [ "shiba_yu36" ] }, { "blog_url" : "http://shibayu36-private.hatenablog.com/", "permission" : "private", "can_be_
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
WebKit Web Socket design doc Authors: ukai, yuzo, tyoshino Status: Draft (as of Sept 2, 2009)
GitLab.com / Runbooks · GitLab