12 Apr
2011
12 Apr
'11
1:11 p.m.
On 4/12/11 4:00 PM, Brent Hilpert wrote:
Agree 100%. During a programming project, I'll compile hundreds of
times in a day. In those days, one might go days or even weeks between
compiles.
This is to say nothing of the fact that (most) people finally figured
out that too much red tape, paperwork, meetings, bureaucracy, and other
distractions are counterproductive and don't generally contribute to
actually getting things done. Many management types seem to prefer
talking about doing stuff more than actually doing stuff.
-Dave
--
Dave McGuire
Port Charlotte, FL
I preferred a
more formal development style. Edit, compile, run,
lather, rinse, repeat. Lots of different source files. The time
saved by using QuickC didn't amount to a hill of beans in the overall
picture.
I find that the more sophisticated and "helpful"the IDE, the more it
tends to disturb my thought processes.
But then, I'm old.
As a student, I was on the tail end of the keypunch/batch era. It was
painful but one good thing it did was instill the notion of doing the
design and coding correctly up-front, and forcing one to think in detail
about your program logic before running it. It was an objective to have
your program compile and then execute correctly the first time it hit
the compiler.
These days, that seems not just quaint but a radical notion.