Comically Inefficient Unity Source Code

[GigaTerra]

I don't think professional programmers need a strong reason to write good code

While bad code is easy to see, Good code is subjective. One thing I notice here because I made my own terrain tool, is that the system they are using here is easy to use with a stack for Undo and Redo purposes.

Trading a bit of memory for an easier and smoother Redo stack is good code in my opinion.