ТЫ НЕПРАВИЛЬНО УЧИШЬ ПРОГРАММИРОВАНИЕ

Core message

• The specific first programming language matters far less than what you learn with it. Focus on fundamentals and transferable concepts rather than searching for a “perfect” language.
• If you want a faster path to employment, choose popular high‑level languages with many job vacancies. Low‑level languages (e.g., C/C++) typically take longer to master.
• Programming learning is engineered and well‑documented: use official documentation and practice problems. There are no secret learning hacks.

Practical learning workflow and resources

Follow a repeating learn/practice cycle:

1. Read official documentation and theory.
2. Solve practice problems that test that theory.
3. Repeat and expand on gaps you discover.

Guidelines:

• Always consult official websites and documentation for languages, frameworks, and libraries — authors usually provide the clearest and most up‑to‑date guides.
• Use practice/problem sites and training materials that include exercises (ekr.org is mentioned as an example).
• For fast‑moving technologies (modern JavaScript frameworks, Node), prefer recently published materials; check book publication year.
• Fundamental books (algorithms, design patterns) remain valuable over time.
• Prefer English materials when possible — they are often more plentiful and higher quality.

Advice about content, tutorials, and videos

• Filter learning content and stick to a planned path. Random recommendations (e.g., YouTube autoplay) will slow you down.
• Before following a tutorial video, check the description for source code. Videos without source code are low value.
• Video vs text: well‑written text or official documentation is often superior for learning technical details.

Projects and portfolio guidance

• Avoid overambitious “big” pet projects early on — novices often burn out on projects they can’t clearly plan.
• Don’t start a large project until you can describe its structure and the technologies you’ll use.
• Prefer small, useful tools that solve real personal problems and can be scaled; these are more likely to become portfolio pieces.
• There’s no universal learning sequence; use job vacancy listings to identify in‑demand skills and the gaps you should fill.

Code review, mentorship, and practice

• Programming is a practical craft: you learn by doing. Write lots of code.
• Get code reviewed — feedback is essential and accelerates improvement.
• Review options:
  • Peer study buddies for mutual code review.
  • Professional mentors (example cost noted ~ $40/hour).
  • Paid/closed communities that include reviews (author mentions such a community).
  • GPT‑style chat for automated code review (prompt your code and ask for critique).
• Regular practice combined with iterative feedback is the most important lever for growth.

Mindset

• Don’t be afraid of mistakes; iterate and learn from them.
• Avoid scattering across too many directions simultaneously — pick a focus early to reduce wasted time.

Mentioned guides, tutorials, and resources

• Official documentation for languages, libraries, frameworks (React, Flutter, Qt cited).
• React website (includes learning problems/examples).
• Training/problem websites: ekr.org.
• Books: use up‑to‑date books for fast‑changing tech; classic texts for fundamentals.
• Paid course highlighted: SkillFactory’s “IT specialist” course (covers career guidance across 10 IT areas, project/case work, portfolio building, job support, refund guarantee). Promo code: Montana.
• The author’s closed Telegram channel and paid/closed IT community.
• GPT chat for automated code review.

Warnings / red flags

• Don’t chase every recommended language or the idea of a single “right” starter language.
• Avoid jumping between many specialties early on (frontend → testing → analytics, etc.) without a clear plan.
• Be wary of tutorial videos that don’t provide source code.

Main speakers / sources referenced

• Video narrator / author (primary speaker in the original content).
• SkillFactory (course provider).
• Framework/library authors and official docs (React, Flutter, Qt).
• Online problem sites (ekr.org).
• The author’s closed Telegram channel and IT community.
• GPT‑style chat (for automated code reviews).