@@ -1,3 +1,4 @@
line 1
line 2
+line 3
new feature codeThis section has covered quite a bit of the syntax and
commands that you will see on a regular basis when
working with Git. You need to spend some time working
with these commands on your local machine and become
familiar with them so you will be ready for the 200-901
DevNet Associate DEVASC exam. Make sure you are
using resources such as Git documentation on any
command you don’t understand or for which you want to
get deeper insight. All of these commands have a
tremendous amount of depth for you to explore.
CONDUCTING CODE REVIEW
Every good author needs an editor. This book wouldn’t
have been even half as understandable if it hadn’t been
for the fact that we had other people check our work for
comprehension and technical accuracy. Why should code
you write be treated any differently? The intent behind a
code review process is to take good code and make it
better by showing it to others and having them critique it
and look for potential errors. When you develop
software, the vast majority of your time is spent by
yourself—just you and the keyboard. Sometimes when
you are this close to a software project, you miss errors
or use ineffective coding techniques; a simple code
review can quickly uncover such issues.
Beyond the aspects mentioned above, why should you
conduct code reviews? The following are a few common
benefits of code review: