Pseudo-code and flow chart algorithms

do colleges or high schools teach pseudo-code and flow chart algorithms nowadays

I don't know if they do, no online programming startups seem to cover it. I think this is a bit of a shame working out logic of an algorithm using pseudocode & flow charts rather than just starting typing is a really good practice for any non-trivial algorithm.

If you are new to programming and now have many languages to choose from then I would think understanding the flow of how software, apps, etc work is a good start before diving into coding. Even though it was not OOP at the time knowing what the program was supposed to do from start to finish made it easier to decide what language to use for it. Nowadays there is so much code and models out there that the newbie would be very confused as to where to begin. I did not realize why I was having such a hard time, since I know how to understand code or can figure it out no matter what code it is, and even edit it, but then I got lost in the whole flow of it as to how it all worked together.

Let's go offline for a minute. When I paint a room I don't just start painting. I assess how it has to be cleaned, what repairs have to be done, then what color and texture is going to be used or if a design also important, then decide what paint brushes and other tools are needed for the project. I also do not want dirt and dust on my fresh paint or in it either so make sure the room is extra clean and can stay that way during the project, even if I want to use a fan. All that is prep work and takes more time and energy than the actual painting itself. It is a professional approach as well.

Same goes for any program or app or website even. You have to figure out what you want it to do and how it will flow in order to get to the output you want before you just start coding. You also have to care about resources not knowing if it will be used on a phone or tablet or laptop or cash register or TV or car function or who knows what in the future. How do you know what language to use aka syntax if you don't know what the program is going to do yet? As technologies change so fast I think it will be very important in order to keep up or update code that is already created. I don't have any syntax of 10 different languages memorized in order to decide what to use for what project. I like to know how others do it without any flow chart at all.

Earlier in the year I was watching a major convention in Sydney where Cisco was talking about everything being connected to the internet in the future, so I feel the logic of how any code flows becomes more important when you don't know how it will be applied in everyday life in the future. Nowadays when creating an app or whatever type of program we have to think more about it's use tomorrow than just today.

A new car looses value as soon as you drive it off the lot, I think in the same way as when a new app is being created, a new idea on how it will be used comes up before you can get it out on the market. You, or someone else, can change your code much quicker to adapt to such changes if you have a good foundation to relate to, or else you might be chasing your tail trying to keep up with 'the next big thing' lol. I am really more talking about how to structure your design or development career in such a way as to keep up with the unknown future uses of it. To be more successful we have to think long term of the unknown in technologies, so focusing on how it all flows together, should be important first. That is my logic anyways based on so many things I have learned and seen for actually five decades.