That would explain a lot of quality problems.
OTOH, they are still there, just that it is unfashionable to call them
that these days.
I've used flow charts, but they're like a last resort when a problem is
too complex to break down, and one is trying to fit it in a reasonable
space (like one A4 page) to visualise the problem space.
But, that was in the '80s and I was programming in assembler, not much
help from smart data structures or anything back then.
I dunno, there's supposed to be a 'flowcode' or such for microcontrollers
or such, I haven't looked at it closely. But they seem to promise
programming as easy as flowcharting?
The OP's query seemed more like they had lots of code, but no idea how
to hook it together, or something, did they lose their way?
Grant.
