Groups | Search | Server Info | Keyboard shortcuts | Login | Register


Groups > comp.os.linux.misc > #81690

Re: The Value of a 2nd Look At Code

From John Ames <commodorejohn@gmail.com>
Newsgroups comp.os.linux.misc
Subject Re: The Value of a 2nd Look At Code
Date 2026-02-02 08:44 -0800
Organization A place where nothing fits quite right
Message-ID <20260202084402.00004b82@gmail.com> (permalink)
References <k3GdnULeTIuAG-j0nZ2dnZfqn_GdnZ2d@giganews.com> <6975f968$0$28050$426a74cc@news.free.fr> <3csdR.1398925$H7H.1265376@fx13.iad> <697dd67b$0$417$426a74cc@news.free.fr>

Show all headers | View raw


On 31 Jan 2026 10:16:27 GMT
Stéphane CARPENTIER <sc@fiat-linux.fr> wrote:

> >> Well, a lot of times, the process stops when it works. I don't
> >> remember who said that code is not finish when there is nothing
> >> more to add but when there is nothing more to remove.  
> >
> > Antoine de Saint-Exupéry  
> 
> OK, I'm not proud to have forgotten that. He was probably more
> speaking about writing books than writing code, but there are a lot of
> similarities in the two processes.

Aircraft design, I believe, but it's a wonderfully cross-disciplinary
philosophy.

> So, I'm happy I never heard about a programmer paid by the line and I
> strongly hope I'll never heard about that.

I doubt anyone's been *paid* by the line, because that would indeed be
*very* exploitable, but lines-of-code as a performance metric has been
unfortunately common throughout the history of commercial computing, at
least in the U.S.

For bosses who don't understand programming and don't want to, it's
easy to think "they're being paid to produce this 'code' stuff, so the
more code they produce, the more value we're getting on their salary."
But that leads (at best) to sloppy, bloated code, and (at worst) to
capable programmers getting fired for not being "productive" enough :/

Andy Hertzfeld of the Mac team has a funny story about this:
https://folklore.org/Negative_2000_Lines_Of_Code.html

(This same idea that it's churning out code that's "the hard part" of
programming - rather than understanding & modeling the problem, coming
up with a robust solution, implementing it efficiently, and finding and
correcting any bugs that end up in the final product - is what drives
the current obsession with automated "AI" coding; if a chatbot playing
dice with language can produce more code in less time for less money,
who needs programmers? Never mind that it's proving to be neither
cheaper nor quicker, and the results are worse...)

Back to comp.os.linux.misc | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-01-24 21:55 -0500
  Re: The Value of a 2nd Look At Code Stéphane CARPENTIER <sc@fiat-linux.fr> - 2026-01-25 11:07 +0000
    Re: The Value of a 2nd Look At Code Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-25 17:14 +0000
      Re: The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-01-25 21:52 -0500
        Re: The Value of a 2nd Look At Code John Ames <commodorejohn@gmail.com> - 2026-01-26 08:18 -0800
          Re: The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-01-26 13:04 -0500
          Re: The Value of a 2nd Look At Code Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-27 01:26 +0000
          Re: The Value of a 2nd Look At Code Marc Haber <mh+usenetspam1118@zugschl.us> - 2026-01-27 08:58 +0100
            Re: The Value of a 2nd Look At Code not@telling.you.invalid (Computer Nerd Kev) - 2026-01-29 08:26 +1000
              Re: The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-01-28 23:10 -0500
        Re: The Value of a 2nd Look At Code Stéphane CARPENTIER <sc@fiat-linux.fr> - 2026-01-31 10:26 +0000
          Re: The Value of a 2nd Look At Code Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-31 19:39 +0000
            Re: The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-01-31 23:57 -0500
      Re: The Value of a 2nd Look At Code Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-26 07:09 -0500
        Re: The Value of a 2nd Look At Code Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-27 01:26 +0000
          Re: The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-01-27 01:23 -0500
            Re: The Value of a 2nd Look At Code The Natural Philosopher <tnp@invalid.invalid> - 2026-01-27 10:24 +0000
      Re: The Value of a 2nd Look At Code Stéphane CARPENTIER <sc@fiat-linux.fr> - 2026-01-31 10:16 +0000
        Re: The Value of a 2nd Look At Code rbowman <bowman@montana.com> - 2026-02-01 03:04 +0000
        Re: The Value of a 2nd Look At Code John Ames <commodorejohn@gmail.com> - 2026-02-02 08:44 -0800
          Re: The Value of a 2nd Look At Code rbowman <bowman@montana.com> - 2026-02-02 21:27 +0000
            Re: The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-02-02 21:06 -0500
    Re: The Value of a 2nd Look At Code ram@zedat.fu-berlin.de (Stefan Ram) - 2026-01-25 17:53 +0000
      Re: The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-01-25 21:52 -0500
    Re: The Value of a 2nd Look At Code Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-25 19:16 +0000
      Re: The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-01-25 21:58 -0500
        Re: The Value of a 2nd Look At Code Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-26 04:33 +0000
          Re: The Value of a 2nd Look At Code Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-26 04:46 +0000
            Re: The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-01-26 01:05 -0500
            Re: The Value of a 2nd Look At Code Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-01-27 01:26 +0000
              Re: The Value of a 2nd Look At Code Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-01-27 05:13 +0000
          Re: The Value of a 2nd Look At Code c186282 <c186282@nnada.net> - 2026-01-26 00:44 -0500
      Re: The Value of a 2nd Look At Code Chris Ahlstrom <OFeem1987@teleworm.us> - 2026-01-26 07:11 -0500

csiph-web