You Can't Scale Up Disorder

Deeeeeeee

You Can't Scale Up Disorder!

Just a hint to all. I am definitely an expert on this topic!

So whatever area of your projects needs work, or area of knowledge is lacking in using GSASER, deal with it!

Then, and only then, can you start going faster and doing more.

Otherwise, you'll end up with a chaotic situation.

Scalability is impossible unless you deal with whatever is keeping you stuck.

At a higher level, any issues will just be magnified!

Deeeeeeee

P.S. I am not yet at any high level, by anyone's definition...hahaha

Deeeeeeee

More good advice:::::

Be organized, friends!

Even simple things like project naming conventions  in SER and keeping detailed notes in projects matter. (HAHA not like I am a model to follow! Use me as the POOR example! )

Keep a GOOD to-do list. Update as required. Save your old lists.

Don't rely on fifty to-do lists. * (I've done this- makes work hellish!)

*If you do need project-specific to-do lists, have a master list of lists...

Also...Date EVERYthing. (Don't live in a fog!)

Comment your custom code. Verbosely! Make it look neat.

For CMSes that you mod, keep a .txt file in the root that cites every file you alter, why, when, and what lines of code. If you don't, you'll be sorry later. (At least I do this..mostly)

Don't overwrite original files when modding! Save file as (e.g.) indexloader.phpORIGINAL or whatever! Don't save as indexloaderORIGINAL.php, unles you want to have it potentially run.

Deeeeeeee

Scaling up chaos just magnifies it.

In a sense, this may be good, as you discover where you need to become more efficient.

Deeeeeeee

Comment your custom code. Verbosely! Make it look neat. (At least I do this..mostly)
For CMSes that you mod, keep a .txt file in the root that cites every file you alter, why, when, and what lines of code. If you don't, you'll be sorry later. 

How this SHOULD have appeared. (I added the parenthesis later!)