**[⬆ back to top](#table-of-contents)**

When you have more than one level of abstraction, your function is usually doing too

much. Splitting up functions leads to reusability and easier testing.

**Bad:**

defparse_better_js_alternative(code:str) ->None:

regexes= [

]

statements= regexes.split()

tokens= []

for regexin regexes:

for statementin statements:

ast= []

for tokenin tokens:

for nodein ast:

**Good:**

defparse_better_js_alternative(code:str) ->None:

tokens= tokenize(code)

syntax_tree= parse(tokens)

for nodein syntax_tree:

deftokenize(code:str) ->list:

REGEXES= [

]

statements= code.split()

tokens= []

for regexinREGEXES:

for statementin statements:

return tokens

defparse(tokens:list) ->list:

syntax_tree= []

for tokenin tokens:

return syntax_tree

**[⬆ back to top](#table-of-contents)**

Flags tell your user that this function does more than one thing. Functions should do one thing. Split your functions if they are following different code paths based on a boolean.

**Bad:**

from pathlibimport Path

defcreate_file(name:str,temp:bool) ->None:

if temp:

Path('./temp/'+ name).touch()

else:

Path(name).touch()

**Good:**

from pathlibimport Path

defcreate_file(name:str) ->None:

Path(name).touch()

defcreate_temp_file(name:str) ->None:

Path('./temp/'+ name).touch()

**[⬆ back to top](#table-of-contents)**