home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.os.linux.misc      Linux-specific topics not covered by oth      135,536 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 135,153 of 135,536   
   Chris Ahlstrom to Charlie Gibbs   
   Re: The Value of a 2nd Look At Code   
   26 Jan 26 07:09:11   
   
   From: OFeem1987@teleworm.us   
      
   Charlie Gibbs wrote this post by blinking in Morse code:   
      
   > On 2026-01-25, Stéphane CARPENTIER  wrote:   
   >   
   >> Le 25-01-2026, c186282  a écrit :   
   >>   
   >>> So ... went at them. Both are now nearly half the   
   >>> size and the logic is much improved and CAN be   
   >>> followed. Only ONE de-facto flag now for a bit   
   >>> that had to be 'adaptive'. Co-running processes   
   >>> are prevented, confirmation that what's supposed   
   >>> to be running IS running now too. Better, more   
   >>> detailed logging.   
   >>>   
   >>> All in about half the space.   
   >>>   
   >>> So ... "I made it work" may be good, but "I made   
   >>> it work WELL" is the GOAL.   
   >>   
   >> It's always like that: first you make it work then you improve it.   
   >   
   > FSVO "improve".  In many cases this means "make money", even   
   > (or especially) at the expense of quality in the traditional sense.   
   >   
   >> 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   
   >   
   >> That's why it's stupid to consider the best programmer as the one who   
   >> produce more lines of code than others.   
   >   
   > Unless you're being paid by the line.   
      
         
      
   >> And, from what I saw, actually, the AI produce a lot of code which must   
   >> be removed.   
   >   
   > Reminds me of my early days when I'd take over maintenance of someone   
   > else's code - or code that "just grew".  I'd typically reduce the line   
   > count by 30% - or even 50% in some cases.   
      
   Heck, I keep finding bugs, created years ago, in my own software   
   projects.   
      
   --   
   	The wise programmer is told about the Tao and follows it.  The average   
   programmer is told about the Tao and searches for it.  The foolish programmer   
   is told about the Tao and laughs at it.  If it were not for laughter, there   
   would be no Tao.   
   	The highest sounds are the hardest to hear.  Going forward is a way to   
   retreat.  Greater talent shows itself late in life.  Even a perfect program   
   still has bugs.   
   		-- Geoffrey James, "The Tao of Programming"   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca