Learning Python from Scratch: Approaches, Knowledge Sources, and Overcoming Barriers
Python attracts developers with its low entry barrier and rich ecosystem, but myths about performance and challenges for junior specialists deter beginners. In an interview with Alexey Goloburdin, author of the book "Typed Python" and the channel "Digitalize," key aspects are discussed: from the pronunciation of the language's name to learning strategies. Both variants—"python" and "pie-thon"—are acceptable in the Russian-speaking community, with the choice depending on context.
The expert emphasizes: code quality is determined by the developer's skill level, not just the language. Python (CPython) lags in speed compared to JavaScript and PHP, but is actively evolving—recent releases promise several-fold acceleration. Alternative implementations on a subset of Python are already available for tasks requiring performance.
Specialist Trajectory: From Freelancing to Product Development
Alexey's journey began in 2003–2004 with an interest in programming in school. His first commercial experience—2007–2008: freelance projects alongside studies. Next—work at MTS (information security), IBS (corporate software for government structures), Oracle, and SAP (presales and sales). The last 10+ years—his own projects: custom development, product solutions like Salesbeat, and education.
The YouTube channel "Digitalize" (170k+ subscribers) started as marketing for Salesbeat but pivoted to programming. Early videos—client reviews of the outsourcing studio (CRM/ERP, telephony integrations, bots, mobile apps)—are kept as a historical archive. Education: Bauman Moscow State Technical University (2011, radio electronics) with honors.
Salesbeat—a service aggregating delivery data for e-commerce. The key: a unified module on the product card shows timelines and costs for federal/local logistics. A buyer from any city sees: "Delivered the day after tomorrow for 240 rubles"—without navigating to separate pages. Development: audience analysis, e-commerce exhibitions, SaaS based on integrations.
Language Comparison: Why Switching to Python from PHP and Go
Experience with Delphi, JavaScript, PHP (primary 2006–2013). Criticism of PHP:
- Low entry barrier leads to poor-quality code—a project can be launched in a couple of evenings without deep study.
- Non-unified APIs and conventions (different argument orders) foster a habit of "as long as it works."
- Shortage of specialists with maintainable code.
Go is simpler for experienced developers but stricter: compact syntax, limitations against complex architectures, gains in performance. For beginners, the barrier is higher than PHP.
Python is slower, but its ecosystem and readability compensate. CPython in C is evolving toward acceleration.
Effective Python Learning: Books vs. Videos
Knowledge sources are multi-level: books (structured knowledge, editing), videos, articles (Habr), chats, colleagues' blogs. Recommendation: combine them, don't limit to one. Books are underestimated by beginners—videos are easier to consume, but quality is lower without verification.
Example analysis: a 9.5-hour stream on "Fluent Python" ("Python. To the Heights of Mastery"). The Room project—a site with IT book ratings. Videos are suitable for review (like Evgeny Popov's courses), but books provide depth. With an interesting topic, learning comes naturally—from camera operation to LLM experiments.
Strategy for beginners:
- Start with basic books on language structure (PEP 8 for style).
- Supplement with videos for practice.
- Study multiple sources on a topic for a complete picture.
- Focus on typing and code maintainability.
- Don't give up when facing difficulties—transition from simple scripts to projects.
Key Takeaways
- Python is suitable for product development and e-commerce thanks to its ecosystem, despite speed.
- Combine books and videos: the former for depth, the latter for practice.
- Code quality is more important than the language; PEP 8 and typing are foundational.
- Products like Salesbeat demonstrate practical application in real-world tasks.
- Don't delete "history"—early projects reflect growth.
— Editorial Team
No comments yet.