Code Cleanliness And Organization

Projects Programming
7

Osgeld:
or

if(blah)

{
 stuff
}




its totally personal opinion, I call that "noobie expanded" but its dead easy to tell where brackets go when you start battle axe hunting a bug

Mainly, it's about how easy it is to see and validate the control structures. This type of thing is completely opaque and requires you to count braces and parentheses to work out what's going on:

if (distance <= 5.08){Serial.println("TOO LOW!");}
  else {
    Serial.print(distance/2.54);
    Serial.println(" in");}
}

My advice is to put every { and } on a separate line with matching pairs indented by the same amount and the enclosed section indented one extra level, as Osgeld shows.

There are other ways to format code, including putting the opening { on the preceding line, which was very popular when we were programming with teletype terminals and space was at a premium. These days that is not an issue and code clarity and correctness is vastly more important.