Boring Python: Code quality
I don&#x27;t work on large python projects, mostly just small scripts that need to work well (integrating with a 3rd party rest api is a good example). I don&#x27;t do CI or unittests but I use git. This is because it takes time and honestly no one outside of myself would care for small stuff like that. But I do run autopep8 and pylint it (I ignore stuff like line being too long,broad exception handling or lack of docs).<p>My concern is a) It needs to be reliable (don&#x27;t wanna spend a ton of time chasing bugs later on) b) How can I write the actual code better? I see what pro devs write and they use smarter language features or better organization of the code itself that makes it faster and reliable, I wish I could learn that explicitly somewhere.<p>I mean, just the 2.7-&gt;3.0 jump was big for me because since I don&#x27;t code regularly that meant googling errors a lot basically. Even now, I dread new python versions because some dependency would start using those features and that means I have to use venv to get that small script to work and then figure out how to troubleshoot bugs in that other lib&#x27;s code with the new feature so I can do a PR for them.<p>I love python but this is exactly why I prioritize languages that don&#x27;t churn out new drastic features quickly. Those are just not suitable for people whose day job is not coding and migrating to new versions, supporting code bases, messing with build systems, unit tests, qa,ci,etc... coding is a tool for me, not the centerpiece of all I do. But python is still great despite all that.