Transitions

Re: Transitions

Sun, 23 Dec 2018 14:52:41 +0000

"Don't believe everything you read on the internet" -Abraham Lincoln

Re: Transitions

Sat, 22 Dec 2018 20:36:46 +0000

I've also heard this attributed to Andrew Carnegie. So I did a little digging. If I see a picture of a famous person with a quote, I assume it's fake until I see otherwise.

Re: Transitions

Sat, 22 Dec 2018 13:30:35 +0000

Lol all of this from me saying I wrote this code a little lazily. To be honest, I say write code however it benefits you. (︶^︶)

Re: Transitions

Sat, 22 Dec 2018 04:33:08 +0000

I choose a lazy person to do a hard job. Because a lazy person will find an easy way to do it.

Bill Gates

Re: Transitions

Sat, 22 Dec 2018 01:11:18 +0000

That depends. Is it easier to lift a 100-pound weight once or a 25-pound weight 4 times? Working harder would say the 100 pound one, but working smarter would say the 25 pound one would be easier. It all depends. At the end, the same thing is being accomplished, it just depends on how you go about it.

Re: Transitions

Fri, 21 Dec 2018 21:06:51 +0000

Working smarter, not harder is literally being lazy since you don't want to work harder.

Re: Transitions

Fri, 21 Dec 2018 20:25:51 +0000

kg583 The way you define laziness is not laziness but rather extreme efficiency. The reason most of us code is to make computers do things for us, ultimately. That might seem lazy, but it is actually the most efficient way of doing things.

Work smarter, not harder :P

Re: Transitions

Fri, 21 Dec 2018 20:12:54 +0000

What I meant as lazy was "I just saw this challenge and want to make something" then went with the first solution I thought of. A for( loop would possibly work better, but I didn't think of that before I made it.

Re: Transitions

Fri, 21 Dec 2018 19:04:56 +0000

I think we are interpreting lazy in different ways. You detest laziness that begets poor code design or outcomes, which is of course to be avoided. I promote laziness that begets efficiency and speed, because a lazy coder can't be bothered with a convoluted solution if an easier one exists.

Re: Transitions

Fri, 21 Dec 2018 18:45:43 +0000

And when you have memory leaks due to lazy coding? When you don’t include error prevention? When you don’t make it user friendly just because you know how to use it? That’s really the best way to code?

Re: Transitions

Fri, 21 Dec 2018 18:33:40 +0000

I've always held that the best way to code is to be as lazy as possible.

Re: Transitions

Fri, 21 Dec 2018 13:41:19 +0000

Lazy coding is the bad way of coding

Re: Transitions

Fri, 21 Dec 2018 11:59:40 +0000

I could, but I was feeling a bit lazy lol.

Re: Transitions

Fri, 21 Dec 2018 00:08:28 +0000

You can use a For loop.

Re: Transitions

Thu, 20 Dec 2018 23:16:48 +0000

Here's mine, just a short little creation using text.

1→A:1→B:1→C Repeat A=11 Output(A,1,"ºººººººººººººººººººººººººº //26 degree signs A+1→A End Repeat B=11 Output(B,1,"OOOOOOOOOOOOOOOOOOOOOOOOOO //26 O's B+1→B End Repeat C=11 Output(C,1,"θθθθθθθθθθθθθθθθθθθθθθθθθθ //26 thetas C+1→C End 1→A:1→B:1→C Repeat B=11 Output(B,1,"OOOOOOOOOOOOOOOOOOOOOOOOOO //26 O's B+1→B End Repeat A=11 Output(A,1,"ºººººººººººººººººººººººººº //26 degree signs A+1→A End Repeat C=11 Output(C,1," //26 spaces C+1→C End ClrHome DelVar ADelVar BDelVar C "

Basically, it fills the screen then clears it. The total storage is 333 bytes. If you are on a monochrome calculator, change the 11 in the repeat loops to 9, and only use 16 characters instead of 26 for the outputs.

For this to be smaller by 2/3 and faster, just remove the first "O" output and the θ outputs. The size becomes 240 bytes.

Enjoy!

Also, Merry Christmas everyone!

UBER

Transitions

Thu, 20 Dec 2018 20:00:12 +0000

Be Creative!!!