What are some of the habits you believe lead to sp...

# random

[Hullaballoonatic]

What are some of the habits you believe lead to spaghetti code in no time?

For me:
• mutating the arguments of functions
• nested blocks with a depth > 2
• more than 3 arguments to a function
• else blocks
• classes with more than one job
• refusing to refactor
• ctrl-c/ctrl-v

[louiscad]

None

[Emanuele Rabino]

• bad naming
• bad abstractions
• abuse of primitive types

[Jiddles]

A “we’ll fix it later”/“It’s good enough for now” mentality
or in a more concrete sense, //TODOs everywhere

[tddmonkey]

A lack of or “tick box exercise” PR process

[oday]

from personal experience, not thinking/planning before coding

[Réunina]

Not taking the time to clean before I start coding and after I am done.

I found that littles regular refactoring is a very very good habit

[Hullaballoonatic]

people that are comfortable using (read: copy) code they don't understand.

[Haomin]

Start to implement functions that already in the standard lib or provided by the language