Archives
- Newer posts
- April 2024
- November 2023
- October 2023
- August 2023
- May 2023
- February 2023
- October 2022
- August 2022
- July 2022
- May 2022
- April 2022
- March 2022
- February 2022
- June 2020
- March 2020
- February 2020
- January 2020
- December 2019
- November 2019
- October 2019
- September 2019
- August 2019
- July 2019
- June 2019
- May 2019
- April 2019
- March 2019
- February 2019
- January 2019
- December 2018
- November 2018
- October 2018
- September 2018
- August 2018
- July 2018
- June 2018
- May 2018
- April 2018
- March 2018
- February 2018
- January 2018
- December 2017
- November 2017
- October 2017
- September 2017
- August 2017
- July 2017
- June 2017
- May 2017
- April 2017
- March 2017
- February 2017
- January 2017
- August 2016
- June 2016
- April 2016
- March 2016
- February 2016
- January 2016
- July 2015
- June 2015
- Older posts
Is Working on an Existing Project a Piece of Cake?
Well, having worked on other people’s code, it is settled that it’s difficult to modify or even understand it in one go. If you are new to that technology and do not have any idea about the flow of the project, then you are doomed.
There are a few things that need to be followed by the fresher for a particular project or technology:
Understanding the Project:
First things first, before touching or even having a glance at the code, always perceive the project flow and understand the project you are going to fix or work with. Without knowledge of the layout of the project, it will be a tedious job for you. Understanding a project becomes easier if there is proper documentation available for it.
Coder’s Approach:
After understanding the project’s flow, you can move on to the code, but understanding the previous coder’s approach to a particular concept is required. Without this, it would be like having a map but not knowing how to use it. Rather than this, you would be better off writing your own code.
Also Read: Did you know these coding guidelines???
Backup:
Before you get your hands dirty and make a mess of the existing code, get a backup of it, which always helps to revert your code.
Get Help:
There will always be a person with more experience than you. If you have any confusion, make sure you ask rather than working alone and building a ticking bomb, which could blow up at any time and you would not have any idea how to put it off.
Debug Step by Step:
There’s always a conflict between the existing code and the newly written one, so take it one change at a time. According to my experience, any changes I made in the code for a new feature always collided with the existing system, so I had to change it and change it again. It is always better to plan out your feature first, how it is going to fit in, and code accordingly, but this won’t relieve you from debugging. Make sure there are no loopholes that will introduce new bugs into your system.
Document Your Features:
Make sure you keep a record of your newly added feature or the changes you have made in the code and how it works. It will help the user as well as the next programmer.
HAPPY CODING…..!!!
Blog written on: 17-05-2018