How Do OOP Programmers Flowchart?
Lew Pitcher queries: "I recently attended a presentation of a code documentation tool that, among other things, produced a flowchart of the analyzed code. The vendor sells this one product for analyzing both mainframe code (COBOL, 390 Assembler, PL1, etc.) and 'distributed' code (C#, Java, C++, Smalltalk, etc). I haven't kept up with the 'modern' techniques (I prefer Nassi-Shneiderman charts, but I still have my flowcharting template), and wondered if modern 'OOP' programmers use flowcharts. If they don't, what is the preferred technique for diagramming an OOP program?"
Flowcharts are a throwback to when computer programming was considered the same as other disciplines like mathematics or engineering.
As we know now, computer programming is something else. It's a combination of stuff and software is almost a living entity that is always changing.
The only people I see using flowcharts are engineers that think they can program or old farts who refuse to accept new ideas.
The ratio of people to cake is too big
Here's $1, go buy yourself a clue. Don't assume people speak your terminology, and don't mince words at the same time.
-
ping -f 255.255.255.255 # if only