Before changing a complex code, consider these pieces of advice carefully.
The code may look like a simple task.
To get a better judgment, think about the dependencies related to it.
If you are not sure, so make sure.
Check the considerations below to save time and despair!
- Get acquainted about all the features related to that part of the code you intend to work on, most important variables and classes involved.
If it is the core, it is necessary to revise all features and dependencies.
—
Do a list, summarized about all features.
—
Get to know all main variables. What they do, what they control and which features they are involved in.
—
If necessary, create a fast model to understand the dependencies between classes.
How they collaborate to perform the tasks you are about to change.
—
— - Grow small.
The best approach is to create a sandbox to reproduce functionalities from the beginning as if you were creating the application from scratch.
One by one feature or procedure.
When you created the first version of ESL, it was done by this process, and it was very successful. Attempts to start big resulted in failures.
—
— - Small changes and test planning.
Create the versioning structure – how are you supposed to handle each change?
Committing, branching?
Create the test planning – a checklist with all the features that must be tested.
Do just one change and apply the test planning.
Don’t skip the checklist. Just one item is enough to invalidate that change.
—
— - Never underestimate a task.
Don’t start working thinking it is just a small thing to make the miracle.
Usually, in the middle of the task, you may get lost about exactly what you’ve done,
Brazilian system analyst graduated by UNESA (University Estácio de Sá – Rio de Janeiro). Geek by heart.