Language reading
Where to read about Go, C++, TypeScript and Python, matched to how much you use each language.
You write four languages, and they do not get equal time. Go carries your projects and gets most of the reading. C++ serves DSA and contests. TypeScript covers a secondary stack. Python is for tooling.
Allocation rule
Language reading follows usage. Whichever language the current sprint needs gets that week's reading slots. C++ is front-loaded into the phase A weeks. Go carries the project weeks.
Pick your language
Go
Primary language for all three projects. Docs first, then internals, then style.
C++
The DSA and contest language. Reference material, not a specialism.
TypeScript
Secondary stack: dashboards, bots, small tools.
Python
Glue language: benchmarks, scrapers, data wrangling.
What each language is for
C++ stays a tool. You need it for online assessments and contests, not a career in it. Skip the language-lawyer rabbit holes, as the operating rules say.
TypeScript is your secondary stack. It never takes project sprint slots from Go.
Python is glue. Its program is deliberately small, because Go and C++ carry the offer.
Each language page follows the same order: learn-first docs, then canonical articles, then rotating blogs.