Software Development Cross Solution - Index of - Free

ump some things for later
390 Chapter 11
Broken Code Magnets
Here are a bunch of things you could do to work your way through the
Mercury Meals code. Put them in the order you think you should do them.
Be careful, though, there might be some you don’t think will be worth doing
at all.
This is a tricky
one. It’s going
to pop up all
over the place,
so we put
it vertically.
Keep track
of things as
soon as you
find them.
You might
decide it’s
not important
later, but
for now,
just record
everything you
think could be
an issue.
File bugs for issues you find.
Once it’s in the
repository, turn you
CI tool loose on it.
This gets your safety
net set up.
And now we can start
thinking about getting it to
work. We’ll talk more about
this in a few pages.
To-Do List
Create a place in your
bug tracker for issues.
Organize the source
code into your standard
src, test, docs, etc.,
directories.
Write a build script.
Put the code in
your repository.
Integrate the code into
your CI configuration.
Write tests simulating
how you need to use the
software.
Download at WoweBook.Com
You need to get the code
building, but you’ll be
finding things you didn’t
know as you go. Set up a
place to capture these
right away so you don’t lose
this information. You’ll need
it to fix things later.
Keeping with the information
theme, you want to capture
how to build the software.
In order to do that, you
need a build script. It’s best
to get the code organized
before you write your script,
though, so you don’t have to
write it, organize the code,
and then change your script.
Next you need to get this
code version controlled. By
organizing it into directories
before this step, you won’t
have to deal with shuffling
around code you’ve already
committed.
You could also make a strong case for
putting this in your repository before
you shuffle stuff around, so you can roll
things back if you mess it up.