09/04/2026
This weekโs #๐๐ฒ๐ฎ๐๐๐ฟ๐ฒ๐ฑ๐๐ฟ๐ถ๐ฑ๐ฎ๐ shines the spotlight on ๐๐ณ๐๐ฎ๐น ๐ ๐ฆ, author of โ๐ ๐ฎ๐๐๐ฒ๐ฟ๐ถ๐ป๐ด ๐๐ท๐ฎ๐ป๐ด๐ผ ๐ข๐ฅ๐ : ๐ฃ๐ฒ๐ฟ๐ณ๐ผ๐ฟ๐บ๐ฎ๐ป๐ฐ๐ฒ ๐ง๐๐ป๐ถ๐ป๐ด ๐ฎ๐ป๐ฑ ๐๐ฑ๐๐ฎ๐ป๐ฐ๐ฒ๐ฑ ๐ค๐๐ฒ๐ฟ๐ ๐ข๐ฝ๐๐ถ๐บ๐ถ๐๐ฎ๐๐ถ๐ผ๐ป.โ He shared a bit about his inspiration & writing experience with usโฆ
๐ค: ๐ช๐ต๐ฎ๐ ๐ถ๐ป๐๐ฝ๐ถ๐ฟ๐ฒ๐ฑ ๐๐ผ๐ ๐๐ผ ๐๐ฟ๐ถ๐๐ฒ ๐๐ต๐ถ๐ ๐ฏ๐ผ๐ผ๐ธ?
โThroughout my career as a developer, I noticed that while Django ORM is one of the framework's greatest strengths, many developers only scratch the surface of what it can do. The same questions about performance, complex queries, annotations, subqueries, and optimization kept appearing in forums and developer communities.
I also enjoy mentoring developers. Over the years, I created cheat sheets and practical notes to help my mentees understand concepts more quickly. I love sharing knowledge, and eventually I realized these resources could benefit a much wider audience. That inspired me to organize my knowledge into a book that helps developers avoid common mistakes, understand how Django ORM works under the hood, and build efficient, production-ready applications with confidence.
My goal wasn't just to explain Django ORM features it was to share the lessons I learned from real-world projects so that others could avoid the same mistakes and become more effective Django developers.โ
๐ค: ๐๐ฒ๐๐ฐ๐ฟ๐ถ๐ฏ๐ฒ ๐๐ผ๐๐ฟ ๐๐ฟ๐ถ๐๐ถ๐ป๐ด ๐ฒ๐
๐ฝ๐ฒ๐ฟ๐ถ๐ฒ๐ป๐ฐ๐ฒ...
โIt was definitely more challenging than I expected. Writing code becomes easier with experience, but teaching someone the concepts in a clear and engaging way is a completely different challenge.
When I submitted my first draft, the feedback I received was that it read more like documentation than a book. That was a turning point. My editor, Shaul, gave me detailed feedback on how to improve the writing, structure the content, and make it more engaging for readers. His guidance made a huge difference throughout the process.
Another challenge was that while writing one chapter, I often remembered topics I had forgotten to include. I would go back, revise previous chapters, and continuously improve the manuscript.
Looking back, I realized that the journey of writing the book was even more rewarding than seeing the published copy. I truly enjoyed every stage of the process.โ
๐ค: ๐ช๐ต๐ฎ๐ ๐ฎ๐ฑ๐๐ถ๐ฐ๐ฒ ๐๐ผ๐๐น๐ฑ ๐๐ผ๐ ๐ด๐ถ๐๐ฒ ๐๐ผ ๐๐ผ๐บ๐ฒ๐ผ๐ป๐ฒ ๐๐ต๐ผ ๐๐ฎ๐ป๐๐ ๐๐ผ ๐๐ฟ๐ถ๐๐ฒ ๐ฎ ๐ป๐ผ๐ป๐ณ๐ถ๐ฐ๐๐ถ๐ผ๐ป ๐๐ฒ๐ฐ๐ต๐ป๐ถ๐ฐ๐ฎ๐น ๐ฏ๐ผ๐ผ๐ธ?
โDocument the problems you solve throughout your career. Keep notes about the challenges you face, the mistakes you make, and how you solved them. Over time, you'll build a valuable collection of real-world knowledge that can become the foundation of a book.
Write the book that you wish had existed when you were learning. Focus on solving practical problems instead of trying to impress readers with complexity. Clear explanations and practical examples are far more valuable than covering every possible feature.
Finally, don't wait until everything feels perfect before contacting a publisher. A good publisher and editor will help shape your manuscript, improve your writing, and turn a good draft into a much better book.โ
๐ค: ๐ ๐ผ๐๐ ๐๐ฒ๐ฐ๐ต ๐ฎ๐๐๐ต๐ผ๐ฟ๐ ๐๐ฟ๐ถ๐๐ฒ ๐ฎ๐น๐ผ๐ป๐ด๐๐ถ๐ฑ๐ฒ ๐๐ผ๐ฟ๐ธ ๐ฎ๐ป๐ฑ ๐ฝ๐ฒ๐ฟ๐๐ผ๐ป๐ฎ๐น ๐ฟ๐ฒ๐๐ฝ๐ผ๐ป๐๐ถ๐ฏ๐ถ๐น๐ถ๐๐ถ๐ฒ๐. ๐๐ผ๐ ๐ฑ๐ถ๐ฑ ๐๐ผ๐ ๐ณ๐ถ๐ป๐ฑ ๐๐ต๐ฒ ๐๐ถ๐บ๐ฒ ๐๐ผ ๐ฐ๐ผ๐บ๐ฝ๐น๐ฒ๐๐ฒ ๐๐ผ๐๐ฟ ๐ฏ๐ผ๐ผ๐ธ?
โLike many developers, I wrote the book alongside my full-time job and family responsibilities. Most of my writing happened early in the morning, late at night, and during weekends. However, I believe the biggest reason I finished ahead of schedule was consistency rather than long writing sessions.
After signing the contract, I created a detailed plan for every chapter based on the milestones. I treated those milestones as commitments and was able to stay ahead of schedule throughout the project.
One habit that really helped me was that I rarely shut down my computer until I went to bed. Whenever I had even a few free minutes, I would go straight to my computer and work on the book. Keeping my computer ready removed the friction of getting started and helped me make the most of every spare moment.
My rule was simple: spend some time on the book every single day, even if it was only five or ten minutes. On days when I found my writing flow, I continued writing until my concentration naturally dropped. On days when I wasn't in the mood to write new content, I reread previous chapters, corrected formatting issues, improved examples, or even refined a single sentence. I considered every small improvement to be progress.
Whenever I realized I was wasting time on something unimportant, I consciously shifted my focus back to the book. Those small, consistent efforts added up over time and ultimately allowed me to complete the manuscript ahead of every milestone.
Most importantly, I couldn't have completed the book without the support of my family. My wife and my sister were incredibly supportive throughout the entire journey, and their encouragement made a huge difference.โ
๐ค: ๐๐ฟ๐ฒ ๐๐ต๐ฒ๐ฟ๐ฒ ๐๐ต๐ถ๐ป๐ด๐ ๐๐ผ๐ ๐๐ผ๐๐น๐ฑ ๐ฑ๐ผ ๐ฑ๐ถ๐ณ๐ณ๐ฒ๐ฟ๐ฒ๐ป๐๐น๐ ๐ถ๐ณ ๐๐ผ๐ ๐๐ฒ๐ฟ๐ฒ ๐๐ฟ๐ถ๐๐ถ๐ป๐ด ๐ฎ๐ป๐ผ๐๐ต๐ฒ๐ฟ ๐ฏ๐ผ๐ผ๐ธ?
โAbsolutely. I would spend even more time planning the overall structure before writing the first chapter. A well-organized outline makes the writing process much smoother and helps readers build their knowledge step by step.
I would also start collecting ideas much earlier. While writing this book, I kept discovering new topics that deserved to be included, which meant revisiting earlier chapters multiple times. Having a more comprehensive outline from the beginning would make the process even smoother.
Every chapter I wrote also gave me ideas for future books and topics to explore. This experience has made me even more excited about writing again.โ
๐๐ผ๐ฟ ๐บ๐ผ๐ฟ๐ฒ ๐ผ๐ป ๐๐ณ๐๐ฎ๐นโ๐ ๐ฏ๐ผ๐ผ๐ธ: https://link.springer.com/book/10.1007/979-8-8688-2589-7
