I've been programming for a couple of decades commercially, and for three decades overall, and I've found that whether you use or don't use a particular code '

I've been programming for a couple of decades commercially, and for three decades overall, and I've found that whether you use or don't use a particular code 'style' matters little for readability and maintenance purposes compared to how well the source is architected and the system designed as a whole. The eye and brain can 'deal' with a lot of different spacing and alignment automatically; OTOH, working out how the code holds together, what data is changed and when, etc, takes real processing power. I'm not worried about expending tiny amounts of thought and processing energy, only lots of it. In the general case, find a coding layout style that seems reasonable and go with it; if you are working with others this will probably mean looking at the established code base and extracting the important style elements. Time is short; spend it on more important decisions about software structure rather than deciding what bow tie it's wearing that particular day.