# Control flow structures vs Pattern Matching

**URL:** <https://forum.elixirforum.com/t/control-flow-structures-vs-pattern-matching/48668>\
**Category:** Discussions\
**Tags:** code-style, deployment\
**Created:** [June 29, 2022, 4:20pm UTC](https://forum.elixirforum.com/t/control-flow-structures-vs-pattern-matching/48668 "2022-06-29T16:20:09Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![TwistingTwists](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/twistingtwists/32/21564_2.png) [@TwistingTwists](https://forum.elixirforum.com/u/TwistingTwists)\
**Post date:** [July 1, 2022, 6:25am UTC](https://forum.elixirforum.com/t/control-flow-structures-vs-pattern-matching/48668/9 "2022-07-01T06:25:15Z")

</div>

I prefer the multiple function heads. Because then i have scan lesser code to understand it.  
The parent function looks pretty too. 😛

> [@rrmartins](#):
>
> ```elixir
> value
> |> URI.parse()
> |> handle_parse()
> |> handle_error_parse()
> 
> ```

Only by reading the main function, i would know what is being done.  
(assuming sensible naming, which is hard as they say)

I prefer understanding a program top to bottom. Especially , in a team. That is, don’t make me touch the details unless i have to.

---

_[View the full topic](https://forum.elixirforum.com/t/control-flow-structures-vs-pattern-matching/48668)._