Yara Zabihi
Yara Zabihi (162)


I am not a writer. But I made a blog page on my website just in case I have a thought to share...

Different Programming Styles

Every program you write that you intend to keep around for more than a couple of hours ought to have documentation in it. Don't talk yourself into putting off the documentation. A program that is perfectly clear today is clear only because you just wrote it. Put it away for a few months, and it will most like take you a while to figure out what it does and how it does it. If it takes you a while to figure it out, how long would it take someone else to figure it out? 


Good style is a subjective matter, and is difficult to define. However, there are several elements common to a large number of programming styles. The issues usually considered as part of programming style include the layout of the source code, including indentation; the use of white space around operators and keywords; the capitalization or otherwise of keywords and variable names; the style and spelling of user-defined identifiers, such as function, procedure and variable names; and the use and style of comments.


Programming styles commonly deal with the visual appearance of source code, with the goal of readability. Software has long been available that formats source code automatically, leaving coders to concentrate on naming, logic, and higher techniques. As a practical point, using a computer to format source code saves time, and it is possible to then enforce company-wide standards without debates.


It is safe to say a programmer will spend more of his/her time maintaining software versus writing it from the scratch, in order for maintenance and future modifications to go smoothly and without problems the programmer needs to follow a set framework. Like a guide that describes basic stuff so when a different coder takes a look at the program, they can understand it. A guide would describe basic rules for how to name the variables, how to name different namespaces, and so on. They would also verify the methods and different variations that would form one class. 


Programmers can have different styles just like different writers write different, but as long as they follow a set guide and add a lot of notes and comments, everything will be alright!





W3 Schools

University of Arizona CSP

Yara ZabihiComment