I've had several people ask me about how well I optimize Correlation, since programmers using it for Ti-Basic programs try really hard to get the most out of their Ti-Basic programs.  Although I carry out as many optimizations as I can, I've only programed in ASM for 1.5 years, and therefore I'm not the greatest optimizer on this website.  Nonetheless,  Correlation displays text faster than Output( and Text( do.

And just like Correlation, ASM programs always run faster than Ti-Basic programs do, even if you're a beginner.  So don't feel bad if you don't know how to make your program the fastest it can be.  It will still run great, it will still run FAST.  Optimization takes practice.

We may offer optimization suggestions, but it's never to critisize...it's to help you get better.  So be proud of yourself for writing an already-fast program.

optimizations as I can, I've only programed in ASM for 1.5 years, and therefore

Only?

I agree with you though Hot_Dog, optimization is very hard, Runer112 seems to be a pro at it.

I consider myself good at z80 asm

You're z80man

Since I don't know Z80 Assembly very well, I don't know any optimization (except for stuff like ld h,0/ld l,5 could be ld hl,5 and jp to jr when shorter). But tricky ones? I have no idea.

One thing I'm good at is memorizing little tricks to cut off lag (I usually optimize purely for speed -- I like fast things ) but I don't consider myself anywhere near a decent level of optimizations per program.  However, I learnt that testing out different things in repeated loops also shows you a few things -- or just looking at a cycle sheet

The thing is, optimization is a stupid thing to do unless:

- you can write z80 code so fast that adding some optimizations won't slow down your programming speed

- you otherwise have a basic structure / functionally have your program working -- optimizations aren't gonna fix something that doesn't yet exist

Another thing I learned is to learn all the optimizations, and WRITE them down, and actually use flashcards -- this is how I learned how to do a few things.  I've been trying to learn z80 assembly for a full year now -- I have mastered everything in the 28 days tutorial, and I still know I have a very far way to go before I become a master. 

Also, WikiTI is a good resource for these things when you lack a portable calc84, BW, or such. . I learned so much stuff there.  Those who haven't checked it out yet should -- it's chock full of rich info that can greatly improve your knowledge and skill.  Kudos to the authors of it

One of the best ways I've found to learn how to optimize code is to look at compiler outputs. While they can make some pretty idiotic mistakes, they often have really brilliant optimizations that you never would have thought of yourself. Also, if you're able to keep track of program flow, try using Self modifying code. It's often one of the best ways to get highly optimized loops.

Personally, I optimize as I go and I rarely find large optimizations when I go back over my code again.  This being said, I code in Basic for the most part, and I've never even finished a decent program in Asm.

I remember you asked me if you could optimize Illusiat 13 at one point, and I told you to wait until I finish it, because I feared I couldn't understand the code anymore after you do so.