Appendix Creference

Sources & further reading

This course is a plain-language synthesis. Here is where the claims come from, and what to read next now that you're building.

Content was distilled from a curated research vault of 27 notes across architecture, patterns, testing, DevOps, security, performance, documentation, tooling, languages and methodologies. Where the vault has no dedicated note — version control is the notable gap — the course teaches the standard practice and says so below.

C.1Module → source notes

Paths are relative to `Wiki/Software Engineering`.
Module	Source notes
01 · What SE is	`README.md`, `Architecture/Design-Principles.md`
02 · First hour	`Tools/Build-Tools.md`, `Tools/Package-Management.md`, `Tools/Static-Analysis.md`
03 · Version control	Standard practice — the vault has no dedicated git note; branching and review are referenced in `DevOps/CI-CD-Best-Practices.md`
04 · Reading code	`Tools/Developer-Tools.md`, `Languages/Language-Agnostic-Principles.md`
05 · Design in the small	`Architecture/Design-Principles.md`, `Patterns/Design-Patterns.md`
06 · Testing	`Testing/Test-Pyramid.md`
07 · Debugging	`Tools/Developer-Tools.md` (debugging section), `Testing/Test-Pyramid.md` (regression tests)
08 · Reviews	`Methodologies/Engineering-Culture.md`, `Methodologies/Agile-Principles.md`
09 · Shipping	`DevOps/CI-CD-Best-Practices.md`, `DevOps/Observability.md`, `Security/Secure-Coding.md`, `Security/Supply-Chain-Security.md`
10 · Start building	`Methodologies/Engineering-Culture.md`, `Tools/README.md`

C.2Five references worth bookmarking

Reference	What it's for	Where
The Twelve-Factor App	Config, logs, build/release/run, disposability — still the clearest checklist for deployable software	12factor.net
OWASP Cheat Sheet Series	Short, practical guidance for auth, input validation, sessions and secrets	cheatsheetseries.owasp.org
Conventional Commits	A commit message convention that makes history readable and generates changelogs	conventionalcommits.org
Semantic Versioning	What major/minor/patch should mean to the people consuming your code	semver.org
Keep a Changelog	A human-readable release history format — useful the first time someone asks "what changed?"	keepachangelog.com

C.3What to read next, in order

1 · Your own test suite

Read the tests you wrote last month. They tell you what you actually understood.

2 · One open-source project you use

Pick a small one, read its README and CONTRIBUTING, fix a typo in the docs, then a small bug. That is the whole apprenticeship in miniature.

3 · Your framework's testing guide

Frameworks change; the pyramid does not. Learn how the tool at hand makes tests fast.

4 · A postmortem from a company you respect

Reading three good public postmortems teaches more about reliability than any checklist.

C.4License and reuse

This course is released under CC BY 4.0: copy it, adapt it, teach from it, including commercially — with credit to Starphix and a link to the license.

The prose, diagrams and exercises are original synthesis built on public research and documentation. The papers, standards and product names remain the property of their authors and are cited rather than reproduced. Prices, model names and benchmark figures date quickly; check them against a current source before quoting them in a classroom or a proposal.

Version

v1.0