Re: Computer programmers' habits in electronics

Jim Thompson wrote:

On Tue, 20 Dec 2005 17:53:16 GMT, Ignoramus10397
<ignoramus10397@xxxxxxxxxxxxxxxxxxxx> wrote:


A newbie question...

As a computer programmer, I am used to programming without drawing
"design diagrams", "flow charts" and other bull***. I just start
coding and try to make sure that I have some working prototype most of
the time, and that I do things nicely.  Usually things work out okay
and programs do their job quietly, as intended.

Not doing too much "design" also helps when the purpose of the program
is not quite known from the beginning, as it usually happens.

I find it very difficult to change this mindset and do any sort of
diagram drawings or some such when it comes to electrics or
electronics. For example, I put together a pretty intricate phase
converter in the last month, for instance, with two motors, some turn
on logic, blah blah. That seemed to work.

What I am worried about is that if I try to do something involving more
than say 20 wires, I would run into a wall and that electronics is not
the same as computer programming. 

So, I am curious if anyone can relate and tell me either just how
mandatory drawing is, and how to get accustomed to it, or how they
make things without detailed plans.

i 


As a circuit designer I've always liked "block" diagramming of a
system before I begin, so I don't create redundant (or useless)
circuit chunks.

So I find it hard to fathom how you can write software without some
similar organizing scheme.

I once took a course at the community college in Pascal (that will
date me :-)

The instructor insisted on using "outlining" which, to me, was trying
to write raw code without any sense of direction.

When I kept using block diagramming she got pissed at me and started
giving me F's on the assignments, in spite of the resulting code being
quite compact.

Then I skipped the final since I could care less about the credit.

So I got a F for the course.

The dean, Shirley something or other, wrote me a letter expressing
concern for my academic future.

I sent her back a note, "Surely Shirley, Aren't you capable of reading
my records?  I already possess a Masters in electrical engineering."

She didn't reply ;-)

...Jim Thompson

Interestingly enough folks have been trying to find structured ways to do this with software for decades, with moderate to good success. The current methodology is called "UML", for "Universal Modeling Language". While the "Universal" is more of a comment on the narrow-mindedness of the software engineering world than on the applicability of UML for anything but software, it is a very handy conceptual tool.

It provides, among other things, a very powerful block diagramming language tailored to designing object-oriented software applications.

So you were right all along, and had a dippy and vindicative instructor.

--

Tim Wescott
Wescott Design Services
http://www.wescottdesign.com
.