SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-Programming Mailing List Archives

Return to [ 03 | January | 2004 ]

<< Previous Message << >> Next Message >>


Date: Sat, 3 Jan 2004 11:08:03 PST8
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-programming@scoug.com
To: scoug-programming@scoug.com
Subject: SCOUG-Programming: QA equals testing, Part One:Detection

Content Type: text/plain

Bob wrote:
>
> Why do I always [get?] duplicate
> messages from this mailing list?

Because you're popular.

> > Then you are burning a bridge. You are, _arbitrarily_,
> > deciding that humans shall no longer need to understand
> > the source -- and you are designing a system which will
> > make it somewhat impossible for humans to do just that.
>
> No, just raising the source to a higher level. There are
> a lot of programmers that can code in a high level language
> that don't have a clue when it comes to assembler, which is
> the output of the high level language.

My perception is that Lynn is trying to eliminate the high-level source
and "compile" directly from the specs.

You're suggesting that it is okay for the programmer to know how to
write high-level without an intrinsic understanding of what happens
underneath, and for some apps (Hello World) I'm sure that's true.

But if you want to start a list of all the times when understanding what
happens with the calls, the drivers, the machine code, etc is necessary
then you don't need me to start the list for you -- you can easily do it
yourself based on your own experiences.

Heck, Bob, I remember _you_ stating that OS/2 is not a real-time
operating system, and how many Visual Basic guys would even know what
you're talking about? How can they possibly be taught how to put
"real-time operating system" in their specs without an understanding of
lag, latency, interrupt stacking and thread priorities? The
intermediate code has to be understandable to humans so that problems at
that level can be fixed.

- Peter

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 03 | January | 2004 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.