"Refactoring Python Code" book update: a few days ago I started moving all code examples to separate files (out of Markdown files) and covering them all with unit tests. That has been great, as I found tons of small typos. #buildinginpublic (1/4)
Using external files is a great idea - each file is fully working code, and in the book I just include the part I need (e.g. I skip imports and some helper functions).
I have the best of both worlds, I have working code and concise examples (2/4)
I have the best of both worlds, I have working code and concise examples (2/4)
It also means whoever buys the book will receive a package of files with code and tests so that they can play with them! I'm super happy with this decision.
I'm using markdown-pp (github.com/jreese/markdow…, now deprecated) to handle including external files (3/4)
I'm using markdown-pp (github.com/jreese/markdow…, now deprecated) to handle including external files (3/4)
Currently the book stands at 159 pages. I have 16-18 more refactoring techniques to add (on top of 30 ones already there) + a picture for each refactoring. I feel I'll end up with 300 pages in the end. (4/5)
Once I'm done I'm really excited about sharing how the book was written, with my favorite editor @Typora and a few small scripts on top of existing tools like pytest and pandoc
• • •
Missing some Tweet in this thread? You can try to
force a refresh
