I'm doing a thing.
I'm pretty stoked to announce that the book I've been working on for the past few months, Practices of the Python Pro, is now available for early access! The first chapter is available for free, and the first three chapters are currently available if you choose to order the book! I'm able to offer everyone 50% off until February 7th by using the code
mlhillard at checkout (please let me know if you have any issues at all).
I'm brand new to writing books, so even though I'm teaching others it's been a huge learning process for me as well. I've been writing blog posts and documentation for a while now, but taking someone on a journey through any concept from start to finish is an undertaking! It's certainly the most I've had to think about grammar for about a decade 😄
The review and editing process has been paramount in helping me teach better. Turning around the edits on a chapter is often the most difficult part of writing, but it's resulted in what I hope is a great teaching pace. My goal with this book is to make concepts used every day by experienced software developers accessible and exciting to those just entering the field, all in the context of Python. I'm covering things like namespacing, separation of concerns, abstraction, testing, and design patterns. Python's popularity means people come into it from all angles, so the book will be a source for anyone looking to take the next step in their software journey!
If you find you're interested enough in the book to buy it in early access I'm hoping you will help me help others by providing detailed feedback about anything that's confusing, misleading, or missing. The DEV community has been one of the most supportive, inclusive, inquisitive communities I've ever been a part of and I want to produce something that embodies these values!
I'm sure that I will have plenty more to write about the book writing experience as things progress. I'd love to answer any questions you have; whether about the book, the process, or anything else!
As software gets more and more integrated into our lives, the industrialization of its crafting process becomes inevitable. But the over-generalization of software engineering can be crushing the creative side of programming.