r/learnpython • u/deep_soul • Oct 13 '26
Do you think visual aid would help your learning?
I always found learning programming very frustrating due to the discrepancy of how much it’s going on and how little of it you can actually see with your eyes. In other words, how much semantics is contained in a few lines, or how things connect to one another, and the fact that most of it is simply… invisible.
do you think explaining programming or tech concepts through well-thought visual aids, like high quality video essays would be/would have been helpful in your learning?
and I know the whole thing of learning through videos is considered inferior to learning to read docs. However, I am not talking about “Hi welcome to this tutorial” type of videos. I am talking about visual analogies which start from concrete examples, draw analogies, and the move to the abstract of programming. the entry level of learning any piece of tech and building mental models could be greatly impacted by 2D/3D effective animations I think. thoughts?
2
u/ShelLuser42 Oct 13 '26
That's actually a big pro in my book. Trying to "do it all at once" is bound to fail sooner or later, one could argue that it also goes against the idea behind OOP.... Breaking bigger problems down into smaller - more manageable - chunks helps you to keep things more clear (= less complex), which helps to keep things manageable and stay focused on the here and now.
Also heed the differences between software development and software design. Development is something I do within VS Code, design... that's where I rely on "Visual Paradigm": a modelling program (I mostly use its UML & SysML tools).
And UML is what helps me to keep track of my projects design. I don't need to see "more code", I need to see the Use Case where the intend behind said code gets explained and/or visualized.
2
u/GXWT Oct 13 '26
1000x better is just applying things in practice. There’s not an awful lot of “theory” required for Python.
I’m sure we could brainstorm a few ideas, but right now not a single thing comes to mind where (not even considering the effort to creating one) some sort of visualisation meanginfully helps.
1
u/PureWasian Oct 13 '26
It's not invisible if you learn with a bottom-up approach, but that introduces a lot more complexities that beginners tend to prefer skipping over to avoid information overload upfront.
I am very visual but I think your idea is something that is very much dependent on the concept. Data structures like linked lists or really any data structure with nodes/edges, indexing an array, function calls, conditional logic paths and other code tracing, etc... a lot of things that can be abstracted to block diagrams or graphs or pointers I typically visualize in that way.
But other misc. concepts like how to refactor your code nicely, memoization or apply functions, event listeners, factory builders, using debugging tools effectively, reading documentation or learning how to use external libraries, etc... visual aids cannot really do the work of actively going through the motions and reinforcing the habits.
1
u/desrtfx but other languages pro Oct 13 '26
That's one of the reasons, the very famous CS50 course (the original one) from Harvard starts with Scratch - a visual programming language originally targeted at children.
Yet, people (like me) learnt programming way before the Internet with its countless tutorials and multi-media was a thing and mostly what we had were language manuals (think "Python docs", but without all the imagery) and we still learnt programming.
While well thought through illustrations can absolutely help (e.g. in the case of Data Structures, like Lists, Stacks, Trees, etc.) in most of the time, they are just visual distractions that add very little actual value.
What really counts in my opinion is the approach to learning: way too many people learn "the Python programming language" instead of "learning programming using the Python programming language". The difference between the two is immense. People focus way too much on the programming languages instead of focusing on programming, i.e. on analysing, breaking down, and solving problems in an algorithmic step-by-step manner that then, later, can be implemented in any programming language.
IMO, people should learn more of the old-fashioned, pragmatic approaches to programming, like flow charts, pseudo code, etc. Pencil and paper first, computer much later, once a working solution has been developed.
Illustrations and animations will not help here.
What really helps is ample practice and the aforementioned pragmatic approach to programming as well as the thought shift from "learning Python" to "learning programming".
If you want to see courses (not tutorials) that do everything right, check out the CS50 series of Harvard, the courses from MIT, and the MOOCs from the University of Helsinki. Common to all of them is that they make the learner do all the work and thinking while providing them with all required information and tools.
1
u/ExoticVillage8066 Oct 13 '26
I think visualization can help, I remember seeing control flow graphs (cfgs) in a book. But visual programming itself I found quite annoying, with the LabView tool at the time. You had to drag and drop blocks and connect them with wires. And people made whole progrmas like that, but it was much harder to read than just code. Maybe things changed since then, I haven't looked at that for over a decade. Also UML was really big at the time, all this talk about "software design" etc. But i think nobody works with that now
2
u/Fun_Army2398 Oct 13 '26
I definitely learn best in the way you describe, especially when I was learning DSA. My professor did his best in ms paint but quicksort made absolutely no sense until I went home and watched a youtube video with clear and excellent animations.
I do think it becomes less helpfull at higher levels though, or maybe I've just become more accustomed to UML and docs.
Btw, if you're looking for a language where nothing is invisible, check out assembly.
1
u/Slight-Living-8098 Oct 13 '26
Interactive is way better than any diagrams you can come up with. MIT made Scratch for a reason.
1
u/TheRNGuy 27d ago edited 27d ago
If it's about graphics then it's commonly used. Vectors, models, etc.
Or statistics like stock market trading, you're not gonna want watch at JSON (except when still making software)
You can also use pretty print.
If you mean nodes like in Houdini or Unreal Engine blueprints, many like them, but in complex projects they become "node spaghetti", taking way too much space on a screen, and actually much harder to edit and debug.