Message from discussion New Forth Website
From: John Passaniti <john.passan...@gmail.com>
Subject: Re: New Forth Website
Date: Tue, 9 Feb 2010 18:53:46 -0800 (PST)
References: <ly%an.81018$BV.firstname.lastname@example.org> <email@example.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Trace: posting.google.com 1265770426 11451 127.0.0.1 (10 Feb 2010 02:53:46 GMT)
NNTP-Posting-Date: Wed, 10 Feb 2010 02:53:46 +0000 (UTC)
Injection-Info: f15g2000yqe.googlegroups.com; posting-host=184.108.40.206;
X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:220.127.116.11)
Gecko/2010010604 Ubuntu/8.10 (intrepid) Firefox/3.0.17,gzip(gfe),gzip(gfe)
On Feb 9, 9:09=A0pm, Hugh Aguilar <hughaguila...@yahoo.com> wrote:
> By comparison, Alfred's site allows people to upload programs.
> Considering that programming supposedly involves writing programs,
> this emphasis on actual programs makes his site significantly more
> useful than C.L.F..
For professionals-- you know, people who actually derive a living off
creating software-- programming is a relatively small and largely
mechanical part of what we do. If you're doing this as a hobby, then
yeah, programming is what you'll focus on because programming is fun.
And as a hobby, if it doesn't meet other people's needs, then no
problem-- they didn't pay for it. Things change when you're actually
paid to develop software for others. It's then that one's focus turns
towards the *hard* parts of development software: determining
requirements, developing specifications, creating architectures, and
thinking about design. You're also going to be concerned with
effective testing and debugging strategies, thinking about
documentation, deployment, and ongoing maintenance. Ad hoc solutions
you coded up for fun don't really cut it when businesses (and the
people they employ) are at stake.
I used to think like you do. Back when I started in my career, I
thought that programming was all about writing code. That view lasted
up until the time that I saw there were developers who were getting
more done in less time with better quality. At first I make the
mistake that many Forthers make and think it was the language or the
tools that was making them more effective. Turns out that wasn't the
case. Turns out that knowing the problem you're trying to solve (that
is, requirements analysis and specification) is key to not wasting
your time coding functionality you don't need, or having to go back
and rework code that doesn't meet requirements. Turns out that
thinking about architecture and design can give a significant boost in
effectiveness by factoring before you even start writing code, and
knowing how you're going to organize it. In short, *thinking* about
the larger act of developing software verses just one part (writing
code) makes all the difference.
I can understand why you would like comp.lang.forth to focus on just
coding and not the many other aspects of programming. The other
aspects are hard. The other aspects are abstract to hobbyists.
> I have uploaded my slide-rule program to his site and have also set up
> a forum devoted to supporting this program. My novice package is also
> available over there. I hope that people can focus on actual
> programming over there, as an alternative to this nest of vipers that
> C.L.F. has become.
You don't take criticism well. I suggest you stay in the hobbyist
realm, since you wouldn't last doing this professionally in any
engineering team I've ever been a part of.