Learning by... Avoiding mistakes
pete at lcsql.com
Sat Mar 23 19:59:40 CDT 2013
Time used to was that flowcharts were essential. Talking about the days of
punched cards/paper tape and overnight compiles. If you screwed something
up, another day goes by before you could fix it so you really needed to pay
I still do flowcharts but just scribbles on pieces of paper to show the
overall flow of a process.
lcSQL Software <http://www.lcsql.com>
On Sat, Mar 23, 2013 at 5:52 PM, Jerry Jensen <jhj at jhj.com> wrote:
> On Mar 23, 2013, at 5:35 PM, Mark Wieder <mwieder at ahsoftware.net> wrote:
> > Cal-
> > Saturday, March 23, 2013, 4:09:34 PM, you wrote:
> >> How many of you use programming flowcharts to prove your answer before
> >> actually begin to code?
> > Where flowcharting starts to fall apart though, is with asynchronous
> > events - you end up with loosely-coupled pieces of flowcharts.
> I recently did a job where I had to poll two asynchronous serial ports.
> Timing had to be somewhat interlocked. Some input was response to stuff I
> sent, including verifying echos, and some was volunteered by the devices. I
> really really needed that flowchart. As I was puzzling over it, the client
> looked over my shoulder and asked "What are you doing, drawing cartoons?"
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the use-livecode