On the dangers of automated refactoring
bobsneidar at iotecdigital.com
Wed Apr 14 18:19:11 EDT 2021
For my part, I call a function and put the result into a variable. I try not to nest fucntions because I cannot easily tell what the result of each function is, making it harder to troubleshoot, and also to read my own code! For that reason my code is fairly verbose.
> On Apr 14, 2021, at 13:06 , Curry Kenworthy via use-livecode <use-livecode at lists.runrev.com> wrote:
> >> The biggest code is the most repetitive and least modular!
> > Not always, but often. I try to aim for the smallest code base,
> > so I think the contest should be to solve a complex problem
> > with the least amount of code.
> Yes, but not brevity for its own sake! Rather for maintainability,
> efficiency, and to avoid the code-org messes that people try to
> refactor their way out of after practicing bad habits.
> The optimal balance of brevity with performance, readability, and maintainability is where we'll find the best code!
> That'll be fairly tight code, but not always the very smallest.
> I do love concise code; I've seen some whopping humongous scripts! :)
> Best wishes,
> Curry Kenworthy
> Custom Software Development
> "Better Methods, Better Results"
> LiveCode Training and Consulting
More information about the use-livecode