I have a very visual thinking style, and I just recently discovered that not everyone does. It also seems to be a scale.
Now I look at my fellow programmers, their ways of explaining, thinking, writing the code, constructing the architecture, and it seems to me people with more conceptual and verbal thinking sometimes have it easier with programming and software engineering.
I find it hard to grasp any complicated logical structure if I can't visualise it, and not everything in SE is easy to put in pictures. I don't really understand concepts when they are explained in words. When I read about "programming patterns" it's like there are some words on a page without any meaning. Same with, say, closure in javascript - I don't understand it when I read about it but a good visual diagram made it somewhat comprehensible, I now have that schema it my head as a reference for everyday coding.
If the code has services, models, objects, functions, etc as ecapsulated entities, I'm doing fine, but more often the code I'm working with is a mess, so usually no, not so fine. Functional programming is hard unless I can picture the functions as some mechanisms or characters.
Instead it seems to be easier for me to interact with UX and product teams, and understand users. I can play scenarios in my head as if I was watching a video. Which is helpful when you are a frontend dev.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I have a very visual thinking style, and I just recently discovered that not everyone does. It also seems to be a scale.
Now I look at my fellow programmers, their ways of explaining, thinking, writing the code, constructing the architecture, and it seems to me people with more conceptual and verbal thinking sometimes have it easier with programming and software engineering.
I find it hard to grasp any complicated logical structure if I can't visualise it, and not everything in SE is easy to put in pictures. I don't really understand concepts when they are explained in words. When I read about "programming patterns" it's like there are some words on a page without any meaning. Same with, say, closure in javascript - I don't understand it when I read about it but a good visual diagram made it somewhat comprehensible, I now have that schema it my head as a reference for everyday coding.
If the code has services, models, objects, functions, etc as ecapsulated entities, I'm doing fine, but more often the code I'm working with is a mess, so usually no, not so fine. Functional programming is hard unless I can picture the functions as some mechanisms or characters.
Instead it seems to be easier for me to interact with UX and product teams, and understand users. I can play scenarios in my head as if I was watching a video. Which is helpful when you are a frontend dev.