Flow Charts
-
Does anyone still use flow charts to plan code? I do and have been using clunky legacy software. Any recommendations for best of breed (preferably near to free)?
-
Does anyone still use flow charts to plan code? I do and have been using clunky legacy software. Any recommendations for best of breed (preferably near to free)?
Nope. I don't know what happened to the DOS-based flow chart program I used around 1990 and I'm unsure where my templates are. I do occasionally use Word for simple diagrams. Edit: I think this is the software, but I can't find the disks and documentation. As I recall, the documentation had a fairly interesting index style. Interactive EasyFlow - Wikipedia[^]
-
Does anyone still use flow charts to plan code? I do and have been using clunky legacy software. Any recommendations for best of breed (preferably near to free)?
I do, but I draw them on paper. I haven't found anything that doesn't take too much effort to use that it distracts me from the logic I'm trying to build. After I've wrapped my own head around the problem I usually just throw them away, but occasionally if some snipped of the flowchart needs to go into documentation (which noone reads anyway) then I'll use GraphViz[^]. It's got a pretty steep learning curve since it's effectively just a declarative programming language, but I feel like it's less time consuming than Visio.
-
I do, but I draw them on paper. I haven't found anything that doesn't take too much effort to use that it distracts me from the logic I'm trying to build. After I've wrapped my own head around the problem I usually just throw them away, but occasionally if some snipped of the flowchart needs to go into documentation (which noone reads anyway) then I'll use GraphViz[^]. It's got a pretty steep learning curve since it's effectively just a declarative programming language, but I feel like it's less time consuming than Visio.
-
Does anyone still use flow charts to plan code? I do and have been using clunky legacy software. Any recommendations for best of breed (preferably near to free)?
You might try draw.io: [Creating a Simple Flowchart in Draw.io Tutorial - YouTube](https://www.youtube.com/watch?v=64MaQYyAN2w). Unless your product will be proprietary.
-
Does anyone still use flow charts to plan code? I do and have been using clunky legacy software. Any recommendations for best of breed (preferably near to free)?
Try Dia[^], for flow charts and so much more!
I'm currently unsupervised, I know it freaks me out too! JaxCoder.com
-
Does anyone still use flow charts to plan code? I do and have been using clunky legacy software. Any recommendations for best of breed (preferably near to free)?
Maybe for High Level architecture as a means to explane to the non-technical persons what we're aiming to achieve, but not for low level code.
-
Does anyone still use flow charts to plan code? I do and have been using clunky legacy software. Any recommendations for best of breed (preferably near to free)?
-
Does anyone still use flow charts to plan code? I do and have been using clunky legacy software. Any recommendations for best of breed (preferably near to free)?
-
Does anyone still use flow charts to plan code? I do and have been using clunky legacy software. Any recommendations for best of breed (preferably near to free)?
For complex processes it does help me to visualize the steps. I use Visio basic flowchart shapes.
Social Media - A platform that makes it easier for the crazies to find each other. Everyone is born right handed. Only the strongest overcome it. Fight for left-handed rights and hand equality.
-
Does anyone still use flow charts to plan code? I do and have been using clunky legacy software. Any recommendations for best of breed (preferably near to free)?
Not generally to plan code, but I use Visutin [Visustin - Flow chart generator](https://www.aivosto.com/visustin.html) to create after-built flow charts. It handles (I think) about 40 different languages from COBOL to Assembly and has some very nice printing to Visio style files and a few other things. You can get a trial version that works for smaller code bases.
A human being should be able to change a diaper, plan an invasion, butcher a hog, navigate a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects! - Lazarus Long
-
Does anyone still use flow charts to plan code? I do and have been using clunky legacy software. Any recommendations for best of breed (preferably near to free)?
-
Does anyone still use flow charts to plan code? I do and have been using clunky legacy software. Any recommendations for best of breed (preferably near to free)?
-
Does anyone still use flow charts to plan code? I do and have been using clunky legacy software. Any recommendations for best of breed (preferably near to free)?
Not flow charts, but I now and then resort to good old data modelling techniques. Many years ago we certainly did enlighten a few customers by constructing Entity-Relationship models of the information flowing in their organization, illustrating how each of their operations related to (and modified) related data. What ofte comes clearly out of an ER model are issues about duplication of information: Where is the authoritative copy located in the model; which are non-authoritative duplicates - I guess this is where we most frequently had people really start rethinking their information handling. Nowadays, with software developers opening an editor and typing "int main(int argc, char *argv[]) {" before they make eye contact with the customer to ask what to put in before the closing brace, "Now, what was your problem?" ... (this is known as "agile" development: Starting to code before you have any clue about what the problem is), I have to be careful with data modeling: I do it only on a whiteboard or on a sheet of paper. If I do it in a file or document, I immediately am drowned by a tsunami of "Waterfall!!!" accusations. In modern design, you are supposed to make an intial "design" (read: main() function) with no understanding whatsoever of the problem at hand. If you later realize that your "design" is poorly fit to solve the problem, you can refer to "need for refactoring" or "legacy issues" or something like that. All of them are euphemisms for "poor planning". (One of my university systems engineering books had a list of "Factors that may delay your project": Every second bullet point was "Poor planning". But that was before the agile days.) If you manage to sneak into the customer negotiations before the contract is signed, e.g. before the agile guys get a chance to enter their first "int main(int argc, char *argv[]) {" in their IDEs, you may succeed in helping the customer understand what to ask for in the contract. Once the contract is signed and the agile process is started, the battle is lost: Refactoring is far too resource demanding right now. And next month. And the month after that. And ... Planning, whether by flowcharts or data modeling ER diagrams, is by definition waterfall, and waterfall is evil. Every up to date developer knows that, and detests either techniqueue.
-
Not generally to plan code, but I use Visutin [Visustin - Flow chart generator](https://www.aivosto.com/visustin.html) to create after-built flow charts. It handles (I think) about 40 different languages from COBOL to Assembly and has some very nice printing to Visio style files and a few other things. You can get a trial version that works for smaller code bases.
A human being should be able to change a diaper, plan an invasion, butcher a hog, navigate a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects! - Lazarus Long
-
Try Dia[^], for flow charts and so much more!
I'm currently unsupervised, I know it freaks me out too! JaxCoder.com
I did... I think I like it...
__________________ Lord, grant me the serenity to accept that there are some things I just can’t keep up with, the determination to keep up with the things I must keep up with, and the wisdom to find a good RSS feed from someone who keeps up with what I’d like to, but just don’t have the damn bandwidth to handle right now. © 2009, Rex Hammock
-
Does anyone still use flow charts to plan code? I do and have been using clunky legacy software. Any recommendations for best of breed (preferably near to free)?
Yeah, I still do. I am "old school" and drawing the flow chart helps me visualize the flow of the logic, especially when I have multiple threads. Yep, I use pencil and paper, too. :)
I stuff the flowchart into the file folder and when it comes to maintenance or enhancement, it reminds what I was thinking when I wrote the program. At my age, I guarantee that I will not remember the original design.
__________________ Lord, grant me the serenity to accept that there are some things I just can’t keep up with, the determination to keep up with the things I must keep up with, and the wisdom to find a good RSS feed from someone who keeps up with what I’d like to, but just don’t have the damn bandwidth to handle right now. © 2009, Rex Hammock
