🏠 Dashboard · ☑ Progress · 🔎 Finder · 📚 Block · ← Previous · Next →
Source: 00C canonical Google Doc. This page preserves the execution-card content while GitHub provides navigation.
Sequence 006 - Understand technology as a prerequisite layer, not the curriculum
Program Orientation | Orientation
| WHEN / PURPOSE — Prevent the program from turning into a data-engineering bootcamp. |
|---|
WHAT YOU SHOULD LEARN
- Technology is learned just ahead of need.
- SQL is strongest priority but starts before Chapter 5, not Chapter 1.
- Python supports repeatable governance/data-management work, not software engineering.
- Later tools appear only when a chapter creates a reason.
WHAT TO READ / STUDY
| Priority | Resource | Open | Use now | Stop point |
|---|---|---|---|---|
| MUST | Technology Competency Roadmap | OPEN | Read philosophy, sequence, target depth and stop boundaries. | Do not start all technology blocks now. |
| SHOULD | Detailed Technology Competency Reference | OPEN | Use only when a technology gate is active. | Reference only for now. |
DO THIS IN ORDER
- Write the core stack.
- Write the “not required” list.
- Identify the first major technology gate.
- Explain why Chapters 1–4 should not be delayed for SQL/Python.
MERIDIAN APPLICATION
Meridian will use tools to make DMBOK concepts observable, not to train a new engineering profession.
STOP / BOUNDARY: Stay inside the current source/skill boundary. Do not pre-learn later chapters or engineering depth.
CREATE / SAVE
Technology boundary note.
YOU ARE DONE WHEN: You can explain the difference between governance-supporting technical fluency and data engineering.
NEXT → Sequence 007
🏠 Dashboard · ☑ Progress · 🔎 Finder · 📚 Block · ← Previous · Next →