Graphics Reference
In-Depth Information
thesite.Becausehewasinarushtocatchhisplane,hefailedto
check his work and ended up creating more issues than previously
existed. Since Mary was unaware that John had made the change,
she went directly to the code that was actually indirectly affected
by the change and accidentally created even more bugs in the site.
How Could It Have Been Avoided?
On top of the lack of communication between the team members
(especially on John
s part), the entire string of events and resulting
errors could have been avoided by simply using version control.
When John made his change, he should have included a note with
the file he updated on the version control server. That note would
have let the team know what change he made and in which file he
made that change. Even if Mary didn
'
'
t see the note to the team,
she would have been able to
her files to the state they
were in before she started making her changes that created so
many more issues. When she rolled them back, the files would
only contain the initial error created by John and she would be
able to make that single change to launch the site on time.
“
roll back
”
Conclusion
As I mentioned at the beginning of this chapter, there will be
aspects of your work that will remain constant from project to
project and there are considerations to keep in mind as you move
between those projects. Once you start to recognize which aspects
are reoccurring and to which ones you need to give special
attention and thought, you can start fine-tuning your plan each
time you start a new piece of work. One benefit to the constants is
that because you know that every project is going to go through a
quality control process, you
ll start catching your bugs before they
even happen, which can actually improve your coding skills. Also,
as time progresses, you will start to be able to tell if a banner will
fit within the file size limitations set by the project specs just by
looking at the design layout, which brings us to Chapter 2.
'
