DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 49IJYo7S1046138
Authentication-Results: delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=qI1ObUGm
X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0AC893858C66
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1729280090;
	bh=XN52w0DAoA/9GuUX5YoyxN3sGpkZPgFaNI46UOZ+1bM=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=qI1ObUGm7N5pd6TPpHNCTmDBbjvcsEmtx2KIwjFG8rvyzuufr4AR1WgCVS+iKIbo2
	 2D9LYRn++uFH1mQ3kCJcIJqtlzlIs56x6dTzmy4HBkdMbTDsIb3KqKHH8oDkarGQaA
	 o6H7csR54g3kEmkn/roKbGtU17mPexCEDg8Sjr9Q=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org ABC383858C42
ARC-Filter: OpenARC Filter v1.0.0 sourceware.org ABC383858C42
ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1729280068; cv=none;
 b=WI2VftN4sZ+I9wpSRrx2RpHcEDJ2zTH0U2Bo0l2LWwxPUOL3oVXiQTNrw8m2zxzCi+H56V9WqzidsNnmQ2zn7s6+EyH3wA9jN1ebN///SQBhzL3+ksJ+0vAPnFntG5nnvqws2JrGHYZ3me4+UFsxKfocBPtV+9o+rlFtq5hRozk=
ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key;
 t=1729280068; c=relaxed/simple;
 bh=6swJjYdPTqMNOes0jrYUdmk19bYYjcktkb74LkfcESg=;
 h=Date:From:To:Subject:Message-ID:MIME-Version;
 b=BEAQfNHbZu3p1E4Ue041WVUIRA+G1X8Yi6N9J+X0JjOnWRimZiUjL5I4N6YKspiEZ6oZsSyJGVMCnAyQ0k18OPatwz2QEypSpx98Mn3Pxnm04BHyIkr6Z6R0724FUbQ0/0Gt+DIjbCJo9Tm3UkluyXC7MbfaDC3IjkLvGmvSga4=
ARC-Authentication-Results: i=1; server2.sourceware.org
Date: Fri, 18 Oct 2024 21:34:25 +0200
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: Re: Computer Science
User-Agent: K-9 Mail for Android
In-Reply-To: <DB9P251MB0063929BD664AC16091A4A27DE402@DB9P251MB0063.EURP251.PROD.OUTLOOK.COM>
References: <MN2PR19MB3855777D95B46933DB4CA81D9A452 AT MN2PR19MB3855 DOT namprd19 DOT prod DOT outlook DOT com>
 <0e734082-ab4f-45bb-a78b-8ec207821217 AT SystematicSW DOT ab DOT ca>
 <CADNLL6dAchOMWFBhryQdOOV4adrp8d=HOHVtD6uJD4JoN6k6uQ AT mail DOT gmail DOT com>
 <9127af9d-6153-b38c-13ec-3106c7be6ee1 AT cs DOT umass DOT edu>
 <CADNLL6fJ+cr2sY_5Gytf+5MupY6BZCxm4+f48h=7QeAZqXHdgg AT mail DOT gmail DOT com>
 <1677515361 DOT 1675869 DOT 1729184772180 AT mail DOT yahoo DOT com>
 <b8a1e6a0-0348-464f-90ee-31ed4abc6c61 AT acm DOT org>
 <DB9P251MB0063929BD664AC16091A4A27DE402 AT DB9P251MB0063 DOT EURP251 DOT PROD DOT OUTLOOK DOT COM>
Message-ID: <901C8D77-36BB-447E-BCFC-3610FF4F9C8E@lists.roth.lu>
MIME-Version: 1.0
X-Spam-Status: No, score=1.2 required=5.0 tests=BAYES_20, HTML_MESSAGE,
 KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, SPF_HELO_NONE, SPF_NONE,
 TXREP autolearn=no autolearn_force=no version=3.4.6
X-Spam-Level: *
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 server2.sourceware.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.30
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.30
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: marki via Cygwin <cygwin AT cygwin DOT com>
Reply-To: marki <cygwin-users AT lists DOT roth DOT lu>
Content-Type: text/plain; charset="utf-8"
Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 49IJYo7S1046138

Very very interesting discussion.

Nowadays many problems seem to be solved by adding another layer of indirection/abstraction which likely absorbs a lot of the increasing processing power, available memory etc. introduced by each new generation of hardware. Eventually, the sheer number of layers will become the problem.

Needless to say, probably almost no one has a holistic view of all of that. Not to even mention detailed expertise of any few of those.

If it's not clear why all of this happens, the answer probably is as always: money.

El 18 de octubre de 2024 21:13:19 CEST, "José Isaías Cabrera via Cygwin" <cygwin AT cygwin DOT com> escribió:
>
>On Friday, October 18, 2024 02:08 PM, Jim Garrison expressed:
>
>> I have an analogy.  Coding is like playing the recorder (fipple-flute,
>> "English flute", etc). Any 6-year-old can learn the fingerings well
>> enough to carry a tune, but drive to insanity anybody within earshot.
>> Learning to code is about as difficult.  In both cases, the gap between
>> knowing the fingerings and playing professionally is tens of thousands
>> of hours of study and practice.
>
>Great statement.
>
>> Most university courses in "software engineering" don't begin to cover
>> the actual knowledge base and, more importantly, internal mental
>> processes, discipline and curiosity required to do quality software
>> development.  I've had to work with "software engineering" PhDs who have
>> no clue.
>
>This is the problem. With today's idea of making everything easier and less difficult, this generation has acquired a taste of entitlement and lack of working hard. With the idea that everything should be given to them, it's hard to be able to acquire the depth and the discipline that is required for your statement above.
>
>The early days of programming in the late 70's and early 80's had, at least, some kind of assembler programming and some basic electronics classes in the curriculum. Once you had understood the depth of what a computer is and how it works, then some easier programming languages classes came (c, RPG, PL/I, COBOL, etc). But the beginning path to becoming a programmer was taking that deep dive in understanding how the hardware (electronics) and the software came together.
>
>So much to say. Thanks for letting me chime in.
>
>josé
>
>-- 
>Problem reports:      https://cygwin.com/problems.html
>FAQ:                  https://cygwin.com/faq/
>Documentation:        https://cygwin.com/docs.html
>Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple