I've actually found most visual programming environments both counter-intuitive (maybe because I'm from the Right Coast, and the visual environments all seem to come from the Left Coast) and counter-productive. Of course, whether visual environments enhance or impair productivity depends quite a lot on what sort of programming one does, and how large and complex the project is. I suspect that visual environments work best on fairly small-scale ("small" is less than about 50,000 significant lines of code) projects which are neither computationally complex , i.e., n-body simulations (see The Art of Computational Science), numerical relativity, global climate modeling, etc, nor require very high performance and auditing standards, such as flight control software.
One thing I tend to find very frustrating about most visual environments is that the accompanying documentation tends to leave a lot to be desired.
emc
Information about American English usage here and here.
Any Northeastern US area jobs? I'm currently unemployed.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
