This week we welcome William Vincent (@wsv3000) as our PyDev of the Week! William is the author of 3 books on the Django web framework, including Django for Beginners. You can find out more about what William is up to on his website where he writes about Python, Django, and more. Let's take a few moments to get to know him better!

Can you tell us a little about yourself (hobbies, education, etc.)?

I have a "non-traditional" background, in that I started my career as a book editor, transitioned into startups on the business side, and finally in my 30s learned how to code and now work as a software engineer and teacher. I basically locked myself in a room for two years and learned how to code, founded my first startup, and went through a lot of ups and downs along the way. I don't necessarily recommend that approach but it's what worked for my family at the time. I'm also a parent to two little girls so that pretty much checks my "hobbies" box these days.

Why did you start using Python?

I started programming in earnest back in 2012 while I was living in San Francisco and working at Quizlet. At the time, the choice was either Ruby on Rails or Python/Django among the other startups I knew. I chose Python because I needed to pick something and I liked the idea that Python could be broadly used beyond just web development, unlike Ruby. In hindsight, Rails would have been an easier choice since the community had far better resources for beginners and Rails has a little more magic baked in, so the learning curve in terms of getting to your first CRUD/auth app is a lot faster. But I knew that I had to commit to just one language at first and I'm stubborn, so Python it was.

What other programming languages do you know and which is your favorite?

I always find it interesting to experiment with other languages. Lisp in particular was mind-blowing. But day-to-day I mainly use JavaScript as my other language of choice. It has some warts, but I really like using it and don't find it off-putting at all. It's become a lot more Pythonic with ES6 features.

What projects are you working on now?

My main focus are my books; I'll have three out this year which feels like a lot but in truth the first one was two years in the making. I also have spent the last few months working with Michael Herman and Jason Parent on a text-based LMS that will be launching publicly soon (probably will be out by December at TestDriven.io).

Which Python libraries are your favorite (core or third-party)?

I think requests is the stock answer for an elegant, well-documented third-party package. Most of what I use these days is Django-related, so a short list includes django-environ   (for environment variables), Django REST Framework, django-allauth   (user and social registration), and django-rest-auth   (out of the box user endpoints).

How did you get starting writing books on Django?

Django for Beginners began as my own personal notes on web development. I remember feeling almost angry after I figured out basic functionality with Django; like, really, that's all it took in code? Why weren't there any complete examples on the web? Why did that take days of my life to work out?

I started djangoforbeginners.com with the vague idea it might someday be a book but it was only at the end of 2016, after a startup I was in was acquired, that I became serious about it. Writing online and seeing reader comments motivated me to keep going and also greatly improved the content. I also began writing on my personal website, wsvincent.com, with the idea that it would be shorter examples of code that I could later expand upon. Traffic on that site has picked up a lot over the last six months.

What did you learn from writing your books and what would you do differently if you could start over?

I wrote up some detailed thoughts on the process of writing technical books. Basically it's a ton of work and then self-publishing is another extra round of work. I definitely understand in a visceral way why there are so few up-to-date Django resources out there. When the framework updates every year you're never "done" with a book and it requires constant maintenance.

To be a good technical author you have to wear three hats: developer, writer, marketer. It's tough to balance all three properly and, especially when you like to code and can make good money doing that, the marketing side of things often doesn't happen at all. It's like open source software in that respect; quality doesn't matter if you don't spend time and energy getting the word out, writing solid docs, etc.

Do you have any advice for other aspiring authors?

Everyone should write. It helps your own learning and it helps the community since we all see the world in different ways. Don't waste time with a fancy layout for your blog; just write and leave room for comments or your email address so readers can contact you. It's the personal touch that keeps it motivating, not the number of zeroes next to page views.

For books, think seriously about what you want to get out of it. Most people have a vague desire to do a book and/or want the associated prestige. For them, going the traditional book publishing route probably makes sense. You'll have a team of people help you along the way and the biggest risk is that you simply won't finish the book at all. It's so much more time than anyone starting out can imagine to actually finish a book. If you want to make meaningful money from the book though, consider self-publishing and be aware you'll need to market yourself.

Is there anything else you'd like to say?

Programming is for everyone. I firmly believe what makes learning to code hard is the lack of good, up-to-date educational resources. I wish it were easier for developers who wanted to teach to find a sustainable way to do so. And I wish students had a formal way to learn this stuff rather than first sitting through abstract lectures on discrete math and data structures without any larger context of how creative and interactive code can be.

If you read a blog post by someone online that helps, please take the time to write them a quick note of thanks. It makes a huge difference. And if you read a book on programming, write a review on Amazon for the author!

Thanks for doing the interview!