I've had similar thoughts during my career - wanting to read others code so I can get a good idea of how they work and how I can learn to replicate. Its not a bad thought, and I'd highly encourage doing it even if the mature projects you know about are very well established and hard to follow/understand. One thing I'd encourage is for you to also look back in history of the commits and code bases. It can be hard sometimes to understand how code evolves over time, but its very important. For example, I just started using this new open source python project for my home security camera setup ( https://github.com/blakeblackshear/frigate ) and I was hugely impressed with how many features there are given its made by a hobbyist! I decided to look back in the commit history and saw the very first, humble, and honest commit "was just" a script to detect objects: https://github.com/blakeblackshear/frigate/blob/72393be6d66e7642343476f5adb4b8e99d613c79/detect_objects.py I hope this little bit of advice is useful and good luck with learning! The hard work will pay off! More on reddit.com

I haven't seen anyone else mention it, but I think Black has some of the best Python code I've ever seen especially considering that it's solving a relatively complicated problem. More on reddit.com

# judge the leap year
 def judge_leap_year(year):
    if isleap(year):
        return True
    else:
        return False

Hm........

More on reddit.com

I had taken pictures of my then-girlfriend via Skype and wanted to rename them from "Skype-snapshot-X.png" to "-YYYY-MM-DD-X.png" with X being the nth picture for that day by reading the creation date. I had help. More on reddit.com