old code
-
I remember this I think, but I can't place it - like something I read a long time ago.
To err is human. Fortune favors the monsters.
Probably because I've been reading science fiction for 50 years and can riff on most of the tropes pretty easily. If you've ever read the Bolo series of books originated by Keith Laumer, that's the tone I was looking for.
Software Zen:
delete this; -
Probably because I've been reading science fiction for 50 years and can riff on most of the tropes pretty easily. If you've ever read the Bolo series of books originated by Keith Laumer, that's the tone I was looking for.
Software Zen:
delete this;Oh you wrote that? I did not expect that. You really had me going. It was bugging me all night. :laugh:
To err is human. Fortune favors the monsters.
-
old code baked in a less elegant time its functions rusty its features, anachronistic every encounter with it reminds me of my past failure of imagination. if I could only think ahead a few more steps i'd never have old code
To err is human. Fortune favors the monsters.
When I look back of my old code, I think to myself, "Holy broccoli, Batman! What great code. Did I actually write that? So eloquent and yet so powerful." To which I hear the reply, "Get away from computer, Granddad. You know it makes you sad."
Nothing succeeds like a budgie without teeth. To err is human, to arr is pirate.
-
old code baked in a less elegant time its functions rusty its features, anachronistic every encounter with it reminds me of my past failure of imagination. if I could only think ahead a few more steps i'd never have old code
To err is human. Fortune favors the monsters.
Although robust enough for general use, adventures into the esoteric periphery of the C shell may reveal unexpected quirks.
-
Oh you wrote that? I did not expect that. You really had me going. It was bugging me all night. :laugh:
To err is human. Fortune favors the monsters.
Thanks :) .
Software Zen:
delete this; -
old code baked in a less elegant time its functions rusty its features, anachronistic every encounter with it reminds me of my past failure of imagination. if I could only think ahead a few more steps i'd never have old code
To err is human. Fortune favors the monsters.
There are only two categories of code (like computers), prototype and obsolete.
Cheers, Mike Fidler "I intend to live forever - so far, so good." Steven Wright "I almost had a psychic girlfriend but she left me before we met." Also Steven Wright "I'm addicted to placebos. I could quit, but it wouldn't matter." Steven Wright yet again.
-
old code baked in a less elegant time its functions rusty its features, anachronistic every encounter with it reminds me of my past failure of imagination. if I could only think ahead a few more steps i'd never have old code
To err is human. Fortune favors the monsters.
-
All my code is old, I am still using Visual FoxPro :laugh: it's tiny (can run it on a pen drive!) and "does what is says on the tin."
-
Probably because I've been reading science fiction for 50 years and can riff on most of the tropes pretty easily. If you've ever read the Bolo series of books originated by Keith Laumer, that's the tone I was looking for.
Software Zen:
delete this; -
Oh you wrote that? I did not expect that. You really had me going. It was bugging me all night. :laugh:
To err is human. Fortune favors the monsters.
Weeeeeell, poop. So I can't use an extra Audible credit to listen the whole thing? This comes under the popcorn-in-the-office rule - you can't just pop a bag, let the buttery aroma fill the place, and then leave for the day and take the popcorn with you. "Did you make enough for everybody?" "No Ma'am." "Then spit it out." :laugh: We also had a similarly unforgiving rule about microwaving fish dishes or leaving a gallon jar of kombucha to ferment in the break room. Honestly, I'd read/listen to the whole thing. I'll look up the author/series and see what's available in a travel-friendly format. Thanks! :-D
-Bob
-
old code baked in a less elegant time its functions rusty its features, anachronistic every encounter with it reminds me of my past failure of imagination. if I could only think ahead a few more steps i'd never have old code
To err is human. Fortune favors the monsters.
:thumbsup: I like it...an ode to old code! :) I encounter my old code every day. It reminds me of how long I've been doing this and how I myself am also getting older. :sigh: I also noticed recently that my sense of time is slipping. Looking through old emails, I found a screenshot of what I thought was a fairly new feature...it was from 4 months ago! Adding features to a product I still consider to be new, I was reminded that this was my Covid project...started in March 2020 with a 5 month deadline (the year without a summer!)...it's now 2 years old! :omg: My company's flagship product is 22 years old, and I was there from the start. :sigh: To quote JG, 'What a long strange trip it's been'.
"Go forth into the source" - Neal Morse "Hope is contagious"
-
old code baked in a less elegant time its functions rusty its features, anachronistic every encounter with it reminds me of my past failure of imagination. if I could only think ahead a few more steps i'd never have old code
To err is human. Fortune favors the monsters.
Yep, that's why all code should be written 3 times: 1) Write it to prove the concept and LEARN 2) Rewrite it for others and clarity 3) Rewrite it again because we are professionals, and our brains will be shot when we come back. The most complicated piece of Code I ever wrote was an insurance rating engine that constantly changed. The "elegant" solution in the end was: (No Goto allowed)
LOOP
// Shared setup code, variable hunting, etc.If Determination_Condition then
RateXXX;
break;// There were about 100 of those.
..
DefaultRate;
break;
END LOOPI was criticized for using the LOOP in a code review, but the challenge to find a cleaner way found nothing. And I brought the last 10 change requests, which effectively tell you WHERE to place the code to exit early. Life is sometimes simple... (And for complexity, consider rules like, they have a home policy, a life policy, and are disabled... Uggh... Only insurance companies)
-
:thumbsup: I like it...an ode to old code! :) I encounter my old code every day. It reminds me of how long I've been doing this and how I myself am also getting older. :sigh: I also noticed recently that my sense of time is slipping. Looking through old emails, I found a screenshot of what I thought was a fairly new feature...it was from 4 months ago! Adding features to a product I still consider to be new, I was reminded that this was my Covid project...started in March 2020 with a 5 month deadline (the year without a summer!)...it's now 2 years old! :omg: My company's flagship product is 22 years old, and I was there from the start. :sigh: To quote JG, 'What a long strange trip it's been'.
"Go forth into the source" - Neal Morse "Hope is contagious"
kmoorevs wrote:
'What a long strange trip it's been'
I have an in-house debugging tool created in 2000 we use a lot that I'm actively maintaining. It's been getting a couple new features over the last few months. Part of the app is a Windows Shell extension for Explorer, which I'm researching on updating for Windows 11. The current extension is treated as a 2nd-class citizen, relegated to the "old stuff we're ashamed of" sub-menu when you right-click on things.
Software Zen:
delete this; -
:thumbsup: I like it...an ode to old code! :) I encounter my old code every day. It reminds me of how long I've been doing this and how I myself am also getting older. :sigh: I also noticed recently that my sense of time is slipping. Looking through old emails, I found a screenshot of what I thought was a fairly new feature...it was from 4 months ago! Adding features to a product I still consider to be new, I was reminded that this was my Covid project...started in March 2020 with a 5 month deadline (the year without a summer!)...it's now 2 years old! :omg: My company's flagship product is 22 years old, and I was there from the start. :sigh: To quote JG, 'What a long strange trip it's been'.
"Go forth into the source" - Neal Morse "Hope is contagious"
-
Yep, that's why all code should be written 3 times: 1) Write it to prove the concept and LEARN 2) Rewrite it for others and clarity 3) Rewrite it again because we are professionals, and our brains will be shot when we come back. The most complicated piece of Code I ever wrote was an insurance rating engine that constantly changed. The "elegant" solution in the end was: (No Goto allowed)
LOOP
// Shared setup code, variable hunting, etc.If Determination_Condition then
RateXXX;
break;// There were about 100 of those.
..
DefaultRate;
break;
END LOOPI was criticized for using the LOOP in a code review, but the challenge to find a cleaner way found nothing. And I brought the last 10 change requests, which effectively tell you WHERE to place the code to exit early. Life is sometimes simple... (And for complexity, consider rules like, they have a home policy, a life policy, and are disabled... Uggh... Only insurance companies)
The most complicated solution I've written was something that allowed you to define a pixel as a series of "channels", each with a name, resolution/bit depth, default value, and min and max value (related to the bit depth but can be overridden) The pixels could then be accessed by individual channel name, or channel index. In addition, you could set the entire value (all channels) as a unit. A pixel could be as large as the machine's maximum word size. Furthermore, to convert to other color models, all you have to do is make it convertible to a pixel with R, G, and B channels and it will figure out the rest. All of this is done at compile time if the information is available at compile time. Even manipulating the individual channels does not yield shift instructions except if the values aren't known at compile time. It simply creates a new constant value. It's pretty crazy.
To err is human. Fortune favors the monsters.
-
It rhymes in binary. :-\
To err is human. Fortune favors the monsters.