Content Index
A frequently asked question is which format is superior for learning a new technology (specifically in software development): a video course or a book/PDF/ePub.
I'll give you the obvious answer upfront: There is no format that is better than the other. The ideal format is the one that best suits your personal needs and preferences. However, below I present my reasons why I prefer the book format.
1. The Book's Fundamental Advantage: Quick Search and Reference
My preference for the book format is due to its versatility and speed as reference material:
The Video Problem: When I return to a technology after a while, I often have gaps about how something was installed or how a specific piece of code worked. My courses are 40-50 hours long, and searching for the exact reference is a nightmare; I have to navigate class by class, minute by minute, since it's difficult to search for the exact content within the video.
The Book Solution: In a book, if I don't remember what a code snippet does, I simply search for the keyword and get the direct explanation. The book offers quick and accurate reference, which is vital when you only need to recall a detail to keep moving forward.
2. Storage and Volatility Aspects
The book format also wins in terms of portability and durability:
Lightness: A book (PDF/ePub) weighs a few KB or MB. I can have an entire library on a tablet or Kindle that weighs negligibly.
Video Heaviness: A 30 or 40-hour course can easily weigh 20 to 30 GB. Not only is it difficult to store, but platforms often limit or complicate its download.
Permanence: A PDF you download is yours (as long as you back it up in multiple locations). Online courses are subject to service volatility (the platform could close, or the course could be unpublished). A PDF is support material that no one can take away from you.
3. Ease of Update (My Particular Case)
For me, as a creator, books are easier to keep up to date:
- Video (Hybrid): Updating a 40-hour course (for example, from Laravel 6 to Laravel 11) is almost impossible to do comprehensively. It results in a hybrid where old and new code coexist.
- Book (Total): Renovating a book is much simpler. References and code examples are quickly updated to the new version (e.g., transition from Laravel 10 to Laravel 11, 12…) without leaving mixed content. This guarantees that the student always receives the cleanest and most recent version of the technology.
Book Update: Django 6
I want to tell you about the changes and updates I've made to my Django book for version 6. As a personal rule, I update this material every time a major version is released. I originally launched this book for Django 4, so this represents the third major update.
Unlike the previous edition, this new release features 40% more new content. I've gone from about 170 pages to over 240, improving not only the quantity but also the quality of the explanations and the visual format.
New Format and Brand Design
I am implementing a new visual style across all my books so they have harmony with one another.
- Typography and Reading: I have increased the font size and spacing to make it easier to read.
- Visual Identity: You will see that I now use a dot pattern and a "letter" format on the covers, which will be my new brand reference.
- Code with Style: I have moved away from limited tools (like Google Docs) to use a format that allows for code syntax highlighting, making technical snippets much more legible.
Community Versions and Courses
It is important to clarify how I handle free material:
- Community Book: It will remain on version 5. I will update the free version to version 6 when Django 7 is released. I do this to prioritize and provide value to those who support the project through payment.
- Access: You can get the community version (over 180 pages) simply by registering your email. It is excellent material to get started.
Integrated Courses: In my academy, I have merged the courses to avoid confusion. Now there is a single Django course where free and paid content are integrated into the same platform.
What's new in the content?
Although frameworks like Django are "conservative" (changes between versions don't break all the code), I have taken the opportunity to strengthen three pillars:
1. Expansion of Existing Chapters
I have rewritten explanations to make them clearer, based on what I've learned teaching over these years.
Project Structure: Now with much more detail on the role of each file.
Git and GitHub: Included from the start as an essential development tool.
Views and Forms: In-depth explanation of the difference between regular forms and ModelForms.
2. Entirely New Chapters
I have added sections that didn't exist before or were very scattered:
- Essential Packages: Use of Django Debug Toolbar, Django Extensions, and tools to improve the interface like Django JET (Tailwind-based).
- Deployment: Guides for uploading projects to PythonAnywhere, Railway, and an introduction to Docker.
- General Aspects: Unification of topics such as Signals, sessions, Flash-type messages, and translations.
3. Artificial Intelligence Integration
I have incorporated a section on how to use tools like Gemini, Claude, or ChatGPT to assist in development:
- Creation of suggested prompts to fix errors.
- Generation of initial mockups (HTML/CSS) so as not to work with ugly interfaces while learning backend logic.
Conclusion
This update is free for those who have already purchased the book or the course on my platform. My commitment is to keep this material relevant for years, ensuring you always have access to industry best practices.
If you want to see a detailed comparison of the indexes or review the new sections on Django Channels and REST API, you can check the link in the description or visit my blog.
4. When is the Video Format Superior?
Despite my preference, video is the dominant format in today's society and has an undeniable advantage in specific contexts:
Complex Graphical Interfaces: If you are learning a technology that involves many windows, icons, buttons, and view management (such as Blender, Unreal Engine, or an IDE like Xcode or Android Studio), video is the best option.
The "Windows" Hell: Reading in a book "click here, then click on option X, then maximize the view" becomes an abstract hell and consumes many pages. It's much more digestible to see the step-by-step with audio and video in real time.
Software with Versions: If the software is constantly updated (like Xcode), video can offer a more faithful demonstration of the latest version than a book, whose printed version can quickly become outdated.
Conclusion: The book is king for quick reference and permanence. However, video is essential when the technology requires a high visual component and explicit interface guidance.