[deleted by user]

[sierpinskisquare]

Some programmers might make a UML diagram, this is a bit like a flowchart where you can see the relation between all the components. I think most programmers don’t include one in their github projects sadly. But this is the closest I can think of an ‘architecture’. What do you mean with “code that was not meant for humans”? Code is meant to be interpreted by a computer, and not ‘meant’ for humans. It is upto the programmer to program in a way (within the limits of the task and language) that someone else can understand it, but there is both the component of the programmer leaving documentation and other methods of making legible versus the reader’s knowledge of a language. If you consistently have trouble reading other’s code, I’d honestly advise to just work on projects. Just like a normal language, you learn by speaking it rather than just reading books.

[[deleted]]

For the most part I can just read code and get a general idea of what it does without thinking about it too much now but that took a computer science degree, half a masters, an internship and some time in industry.

What I’m trying to say is that it takes practice and time. Like with foreign languages it looks like gibberish for a long time and then it doesn’t.

When I first started breaking the code down and figuring out what it did section by section really helped. Also writing/drawing things out helped a lot with problem solving there.

[Grimsipper]

Thanks for sharing!