Foundations & languages
Before frameworks and cloud, align on language semantics, memory, and concurrency—they shape bug classes, performance ceilings, and how teams communicate. Use this chapter as a reference for selection, code review, and performance triage.
After this chapter you should: articulate core tradeoffs for a language; spot data races and deadlock patterns; attribute slowness to allocation, algorithms, or I/O instead of swapping libraries blindly.
Scope
| Topic | Notes |
|---|---|
| Languages & selection | Type systems, ecosystems, team skill curves |
| Concurrency & performance | Threads, coroutines, async I/O, measurement |
Tie-in to architecture · layering: fundamentals answer how code runs correctly; architecture answers how modules are organized.
Articles
| Topic | Page |
|---|---|
| Languages & selection | languages |
| Concurrency & performance | concurrency |
See also
- Domain hub and order: Software development
- Delivery: Git workflow, CI/CD