The Official TBR Silliness Thread---2023

[240B]

@240B

I have been informed by  a reliable source that living causes dying.

The most famous example is butter. Decades ago, all the so-called 'studies' said that butter is deadly and everyone should use margarine.
Now, all the so-called 'studies' say that margarine is much worse that butter for health. Who knows?
I'm still waiting for the so-called 'studies' to bring back lard instead of corn oil. LOL

[240B]

[240B]

Another example of: Islam is Insane!

[240B]

https://www.youtube.com/watch?v=qEQyAKzi0pw

[Smokin Joe]

The most famous example is butter. Decades ago, all the so-called 'studies' said that butter is deadly and everyone should use margarine.
Now, all the so-called 'studies' say that margarine is much worse that butter for health. Who knows?
I'm still waiting for the so-called 'studies' to bring back lard instead of corn oil. LOL

I quit paying attention when they said Bleu Cheese causes cancer back in the '70s. I eat what makes ME feel good.

[Slide Rule]

[240B]

[240B]

[Smokin Joe]

Tell me he's riding a step-through or a moped...

[sneakypete]

@240B

Well,he IS riding a moped,which should have been a sure tip as to his intelligence.

[deb]

The only thing missing is a mask.

[240B]

I though it was just me! Don't know how many of you write code, but it is true.
Come back to code I wrote a month ago, have no idea what is going on.
Even though I wrote it, it is all brand new to me.

[Cyber Liberty]

I though it was just me! Don't know how many of you write code, but it is true.
Come back to code I wrote a month ago, have no idea what is going on.
Even though I wrote it, it is all brand new to me.

Correct!  I coded for years and spotted this phenomena very quickly.  That's when I decided I had to add a lot of in-code remarks about what I was trying to do.

[Polly Ticks]

Correct!  I coded for years and spotted this phenomena very quickly.  That's when I decided I had to add a lot of in-code remarks about what I was trying to do.

* PT - Comments are definitely important! 

[240B]

* PT - Comments are definitely important!

Got into BIG trouble with this once. I was tasked by upper senior management to give a presentation (with the code) on a application (real working application, not a phone app) I wrote. Didn't think anything of it. Essentially, I just ignored reviewing the code thinking, I wrote it. I know it.

The presentation collapsed. Complete failure. Without knowing it, I had forgotten everything. It was disaster which did put a mark in my file and set my career back a bit. I recovered but it took a while. It was then I learned to never take anything for granted. And ALWAYS REHEARSE any presentation with a handful of collogues. I was overconfident and cocky. It bit me in the butt.

[DB]

I though it was just me! Don't know how many of you write code, but it is true.
Come back to code I wrote a month ago, have no idea what is going on.
Even though I wrote it, it is all brand new to me.

Try switching between VHDL, Elixir, Phoenix, C and FreeBASIC... Ack!

[Kamaji]

I though it was just me! Don't know how many of you write code, but it is true.
Come back to code I wrote a month ago, have no idea what is going on.
Even though I wrote it, it is all brand new to me.

Yup.  That's why comments are the go-to.  Comments before you code to outline/structure it; comments while you code to keep tabs on what you're doing; comments after you finish coding so you remember what you eventually ended up with, and why it isn't at all what you intended to do when you started out (see first set of comments).

[DB]

One of the best (worst) things about going back to older code you wrote is you look at something and say that was stupid and cleverly simplify it. Then only to discover there was some subtle but critical reason why you did it that way previously...

[Kamaji]

One of the best (worst) things about going back to older code you wrote is you look at something and say that was stupid and cleverly simplify it. Then only to discover there was some subtle but critical reason why you did it that way previously...

[240B]

One of the best (worst) things about going back to older code you wrote is you look at something and say that was stupid and cleverly simplify it. Then only to discover there was some subtle but critical reason why you did it that way previously...

It is like a trance. You get onto a highway, a way of thinking with a purpose and a goal. Singularly fixated in the moment on weaving all your code together into a tapestry of function. Then when the trance breaks, you have to go back to review what you just did, and why.

The Greeks had muses. The muses which are instruments of inspiration from the Gods, were responsible for extraordinary artistic accomplishments by mortals (people). Great poems, great plays, great speeches, extraordinary mathematics, advanced ideas, were all the muses (messengers of the Gods) using mortals as their instruments.

Writing one of a kind great code is a work of art. There must be some muse which inspired it. Going back a month later and trying to figure out what the muse was doing is difficult, because you are no longer imbued with the devine inspiration you had at the time.

[240B]

[Kamaji]

[Kamaji]

[roamer_1]

I though it was just me! Don't know how many of you write code, but it is true.
Come back to code I wrote a month ago, have no idea what is going on.
Even though I wrote it, it is all brand new to me.

I am obsessive when I code. Even brand new code, I MUST keep the whole thing spun up in my head... Eventually, after a marathon session, I crash and burn, and the whole dang thing comes crashing down in my head... nothing but embers... after 14 hours of sleep, I have the labor of spinning it all back up in my head, brick by brick...

So yeah, when I have to do a rewrite or repair, it might as well be someone else's code... other than my commenting and peculiar adherence to structure, which is a comfort.

[corbe]

   I'm old school, I started coding in 72 w/USAF~SAL/PAL (System Assembly Language/Program Assembly Language) on a Univac 1050-II.  It usually involved Punch card operators/Sorters and a Reader in the Computer Room.



   I later wrote in a variety of RPG's and JCL, dabbled in COBOL.