One of my big goals as a developer of late has been what I call the water principle… (“Be water.” - Bruce Lee. (Yes, the irony of quoting Bruce Lee isn’t lost on me)) Developing should be as simple as possible. When I start a new project, my setup should be as close to a single pushbutton as possible. It should flow like water. For this, I have created my Dev Playbooks. Simple, GitHub templates that I can leverage for the languages I am working in. I go boop, and I have a repo ready to go with all the things I like to have when I am coding something. Things like CI/CD, testing dependencies, etc.
There is one language that I have found completely illusive in this quest: Python. The language is one of the most wonderful I have ever coded in, supported by the worst heaps of shit, dung pile, all over the fucking place, bullshit I have ever seen. My only conclusion is that the language has been infested by scientists who couldn’t keep their kitchens clean, let alone a codebase. I picture the typical Python developer in a room filled with discarded Pizza Hut boxes, dirty clothes, bottles filled with urine, and cat boxes that haven’t been emptied in several weeks.
I have one fundamental existential question regarding any task I embark on: How do you do it? When it comes to Python, that answer is invariably, fuck if I know. It shouldn’t take a whole book to document one subset of a subject that, in any non-Edward Scissorhandish programming language, would take up a few lines on a README.md.
Every now and then, I hobble onto my whaler and send it back out onto the choppy seas of Pythondia in the apparently futile hope that I will find something that once and for all. Today is another of those days. Maybe the Python Project Wizard will be the answer to my pathetic dreams. We shall see...