Reflective Writing 2

1. Look up the term “coding convention” and briefly define what one is.

Coding conventions are unofficial rules programmers are encouraged to follow for specific programming languages to make code more readable.

2. What is the benefit of everyone in a team adhering to a convention like this?

Programmers will be able to quickly and easily understand code written by another person.

3. Is there any benefit to sticking to a convention even when you’re working alone?

You may make your code open source someday or somebody else might take over work on the code or you might ask for help.

4. Is there any downside to coding conventions?

I think that strict coding conventions can limit what people want to write and also limit what people think is possible or doable.

5. What are the areas addressed in the Google guide that you are most surprised are specified?

I’m surprised by the way they organize methods. There is supposed to be some logic to it, but the exact organization is determined by the programmer.

6. In what areas does your own code not meet these standards?

I sometimes press tab instead of the spacebar for spacing, and in multi block statements (if statements) I will sometimes space the brackets {} “wrong”.

7. How would you feel about being forced to use this style for the programs you write?

If it’s not too far off from what I already do, it won’t be too tedious. I might get upset if some specific rule is time consuming and deemed unnecessary.