-
Notifications
You must be signed in to change notification settings - Fork 0
docs: expand source quality audit and methodology transparency #2
New issue
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
Open
cboone
wants to merge
14
commits into
docs/certainty-calibration-pass-20260302
Choose a base branch
from
docs/source-quality-audit-20260302
base: docs/certainty-calibration-pass-20260302
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 10 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
2589b8b
docs: begin source quality audit in key report docs
cboone 6d79729
docs: continue source quality audit with attribution and caveats
cboone e1f86e7
docs: strengthen source quality in agile go and show hn reports
cboone 881f6c6
docs: tighten bibliography sources and add citation links
cboone 067eb03
docs: add evidence basis notes to self reports
cboone 35b4db5
docs: add source quality notes to terminal and font guides
cboone e7d9e0b
docs: add source quality framing to three major reports
cboone 078c847
docs: strengthen source quality notes in core analyses
cboone 1b07cc7
docs: add evidence framing across llm-agent reports
cboone 054472a
docs: add evidence basis notes to historical and language studies
cboone c9c6285
docs: clarify evidence quality in go cloud-native report
cboone 584f2c0
docs: improve methodology transparency in comparison reports
cboone 82296d4
docs: add methodology transparency to format and platform reports
cboone 08300f7
docs: add methodology transparency to llm workflow guides
cboone File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -10,7 +10,16 @@ This bibliography accompanies the comprehensive history of agile methodology, or | |||||
|
|
||||||
| --- | ||||||
|
|
||||||
| ## Primary Sources and Foundational Documents | ||||||
| ## Source quality note | ||||||
|
|
||||||
| - **Primary sources:** Original manifestos, standards, books, conference material, and vendor/organization first-party publications. | ||||||
| - **Secondary sources:** Academic synthesis papers, analyst reports, and historical overviews. | ||||||
| - **Tertiary sources:** Encyclopedias and commentary sites, useful for discovery but lower confidence for factual claims. | ||||||
| - **Usage guidance:** Prefer primary and secondary sources for substantive claims in narrative reports; treat tertiary links as orientation material. | ||||||
|
|
||||||
|
Comment on lines
+13
to
+19
|
||||||
| --- | ||||||
|
|
||||||
| ## Primary Sources and Core Documents | ||||||
|
|
||||||
| **The Agile Manifesto and History** | ||||||
| - Agile Alliance. "History: The Agile Manifesto." [https://agilemanifesto.org/history.html](https://agilemanifesto.org/history.html) | ||||||
|
|
@@ -31,7 +40,7 @@ This bibliography accompanies the comprehensive history of agile methodology, or | |||||
| **Scrum** | ||||||
| - Schwaber, Ken, and Mike Beedle. *Agile Software Development with Scrum*. Prentice Hall, 2001. [https://www.amazon.com/Agile-Software-Development-Scrum/dp/0130676349](https://www.amazon.com/Agile-Software-Development-Scrum/dp/0130676349) | ||||||
| - Schwaber, Ken. *Agile Project Management with Scrum*. Microsoft Press, 2004. [https://www.amazon.com/Agile-Project-Management-Scrum-Developer/dp/073561993X](https://www.amazon.com/Agile-Project-Management-Scrum-Developer/dp/073561993X) | ||||||
| - Sutherland, Jeff. *Scrum: The Art of Doing Twice the Work in Half the Time*. Crown Business, 2014. [https://www.goodreads.com/book/show/19288230-scrum](https://www.goodreads.com/book/show/19288230-scrum) | ||||||
| - Sutherland, Jeff. *Scrum: The Art of Doing Twice the Work in Half the Time*. Crown Business, 2014. [https://www.amazon.com/Scrum-Doing-Twice-Work-Half/dp/038534645X](https://www.amazon.com/Scrum-Doing-Twice-Work-Half/dp/038534645X) | ||||||
|
|
||||||
| **Lean Software Development** | ||||||
| - Poppendieck, Mary, and Tom Poppendieck. *Lean Software Development: An Agile Toolkit*. Addison-Wesley, 2003. [https://www.amazon.com/Lean-Software-Development-Agile-Toolkit/dp/0321150783](https://www.amazon.com/Lean-Software-Development-Agile-Toolkit/dp/0321150783) | ||||||
|
|
@@ -42,7 +51,6 @@ This bibliography accompanies the comprehensive history of agile methodology, or | |||||
|
|
||||||
| **Continuous Delivery and DevOps** | ||||||
| - Humble, Jez, and David Farley. *Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation*. Addison-Wesley, 2010. [https://www.amazon.com/Continuous-Delivery-Deployment-Automation-Addison-Wesley/dp/0321601912](https://www.amazon.com/Continuous-Delivery-Deployment-Automation-Addison-Wesley/dp/0321601912) | ||||||
| - Humble, Jez, and David Farley. *Continuous Delivery* (Goodreads page). [https://www.goodreads.com/book/show/8686650-continuous-delivery](https://www.goodreads.com/book/show/8686650-continuous-delivery) | ||||||
|
|
||||||
| **User Stories and Estimation** | ||||||
| - Cohn, Mike. *User Stories Applied: For Agile Software Development*. Addison-Wesley, 2004. [https://www.amazon.com/User-Stories-Applied-Software-Development/dp/0321205685](https://www.amazon.com/User-Stories-Applied-Software-Development/dp/0321205685) | ||||||
|
|
@@ -52,16 +60,14 @@ This bibliography accompanies the comprehensive history of agile methodology, or | |||||
| ## Academic Papers and Historical Research | ||||||
|
|
||||||
| **Iterative Development History** | ||||||
| - Larman, Craig, and Victor Basili. "Iterative and Incremental Development: A Brief History." *IEEE Computer*, June 2003. [https://www.craiglarman.com/wiki/downloads/misc/history-of-iterative-larman-and-basili-ieee-computer.pdf](https://www.craiglarman.com/wiki/downloads/misc/history-of-iterative-larman-and-basili-ieee-computer.pdf) | ||||||
| - Web3us. "Iterative and Incremental Development: A Brief History." [https://www.web3us.com/how-guides/iterative-and-incremental-development](https://www.web3us.com/how-guides/iterative-and-incremental-development) | ||||||
| - WebSeitz Wiki. "(2003-06-30) Iterative and Incremental Development: A Brief History." [http://webseitz.fluxent.com/wiki/2003-06-30-IterativeAndIncrementalDevelopmentABriefHistory](http://webseitz.fluxent.com/wiki/2003-06-30-IterativeAndIncrementalDevelopmentABriefHistory) | ||||||
| - Larman, Craig, and Victor Basili. "Iterative and Incremental Development: A Brief History." *IEEE Computer*, June 2003. [https://doi.org/10.1109/MC.2003.1204375](https://doi.org/10.1109/MC.2003.1204375) | ||||||
|
||||||
| - Larman, Craig, and Victor Basili. "Iterative and Incremental Development: A Brief History." *IEEE Computer*, June 2003. [https://doi.org/10.1109/MC.2003.1204375](https://doi.org/10.1109/MC.2003.1204375) | |
| - Larman, Craig, and Victor Basili. "Iterative and Incremental Development: A Brief History." *IEEE Computer*, June 2003. DOI: [https://doi.org/10.1109/MC.2003.1204375](https://doi.org/10.1109/MC.2003.1204375) · Author-hosted PDF: [https://www.craiglarman.com/wiki/downloads/misc/history-of-iterative-larman-basili-ieee-computer.pdf](https://www.craiglarman.com/wiki/downloads/misc/history-of-iterative-larman-basili-ieee-computer.pdf) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -10,6 +10,12 @@ _January 25, 2026_ | |||||
|
|
||||||
| The ecosystem has settled into distinct niches rather than crowning a single successor. YAML is widely used in DevOps (Kubernetes, GitHub Actions), TOML is widely used in package management (Cargo.toml, pyproject.toml), and JSON holds firm for machine-to-machine APIs. Emerging formats target specialized needs: KDL for human-friendly documents, RON for Rust type safety, and Dhall for programmable configs designed to avoid non-termination. | ||||||
|
|
||||||
| ## Method and source quality | ||||||
|
|
||||||
| This comparison prioritizes language specifications, official project documentation, and ecosystem standards (for example PEPs and primary language docs). | ||||||
|
||||||
| This comparison prioritizes language specifications, official project documentation, and ecosystem standards (for example PEPs and primary language docs). | |
| This comparison prioritizes language specifications, official project documentation, and ecosystem standards (for example, PEPs and primary language docs). |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR description says the source-quality audit work begins in three docs (agile bibliography, Show HN guide, and the LLM agent monitoring tools report), but this PR also updates many additional documents across other folders (terminal, fonts, data-formats, etc.). Consider updating the PR description (or splitting the PR) so the stated scope matches the actual change set for reviewers.