this post was submitted on 01 Sep 2023
339 points (96.2% liked)

Programming

17670 readers
211 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] StudioLE@programming.dev 7 points 1 year ago (2 children)

Yep. And three functions is better than one for legibility even if one would be fewer lines of code

[–] Feathercrown@lemmy.world 6 points 1 year ago (1 children)

I think it really depends. Functions break up the visual flow, so if you need to look at multiple functions to visualize one conceptual process then it can be less efficient

[–] Buttons@programming.dev 4 points 1 year ago

Yes. I learned this from Haskell. I like Haskell, but it has a lot of very granular functions.

Earlier comment said that breaking up 1 function into 3 improves readability? Well, if you really want readability then break it up into 30 functions using Haskell. Your single function with 25 lines will become 30 functions, so readable (/s).

In truth, there's a balance between the two. Breaking things up into function does have advantages, but, as you say, it makes it more likely that you'll have to jump around a lot to understand a single process.

[–] gornius@lemmy.world 1 points 1 year ago

I specifically have a rule that if at the current abstraction layer, a step is more than one function call/assignment - I'm creating another function for that.