6/24/2023 0 Comments Macs fan control yc hacker redditThis is the kind of codebase you get when you have people who have been writing code for a long time, but never in the context of a software engineering project alongside experienced software engineers they can learn from. Like I said, they can write clever code, but there’s a difference between bashing on code until it works and building it properly. No, but it is a project made by people lacking software engineering skills, which is a distinction I drew in my earlier comment. > This is not a project made by people without dev skills. Unless it’s code released by researchers, etc. Not all Python software gets all of this right, but it’s incredibly rare to have so many misses, even for hobbyist developers. Why is there precisely one test (that has nothing to do with the core functionality)? Why is the Git history full of things like “finish”, “correct merg”, “fix more”, “add code”? Where is the linting config? Why are there print statements everywhere? Why does non-UI code have UI code embedded in it? Why is there random code commented out? Why is there no consistency across the codebase? Why is everything written as if they’ve never seen a Python project before (comments that should be docstrings, docstrings that should be comments, print("WARNING: ") instead of using logging or warnings, underscores in CLI flags, no shebangs in scripts intended to be run from the command line…) ![]() ![]() Really? I find the difference between the Stable Diffusion code and the code you find in a typical Python package to be night and day.
0 Comments
Leave a Reply. |