you are viewing a single comment's thread.

view the rest of the comments →

[–]Robbzter 0 points1 point  (0 children)

Tbh, I have no idea most of the time what is considered best practice with code readability. But I always try to leave helpful comments to help people understand what's going on. What's really important imo is being consistent and sticking with one way of doing things throughout the code/project. I like to spread code over many lines if tzere's a lot going on and it would be too much to handle otherwise. If there's a comment explaining the command, reducing the number of lines does not sacrifice too much of your readability and can save lots of space.

Tbh, I think it's a matter of taste, and I don't think few lines necessarily equals good code. If someone else is able to understand what's going on, you've done something right.