Answer the question
In order to leave comments, you need to log in
How to change something in software projects?
In general, I can’t figure out how to change anything in software projects. The teacher advises quite old books from 2004, but I don’t know if it’s worth reading rather old literature, or does the system for organizing projects change every year and I need more modern literature? Or maybe there is some universal book related to my problem?
Answer the question
In order to leave comments, you need to log in
Most of the books that were released yesterday are based on knowledge that someone got in 2004, so even old books are always full of useful information.
As for changes in the project - so if you know how to program - you should know what to change. If you can't, don't change.
Or clarify your question.
This is elementary - it is enough to know how elementary functions work and build a structure diagram in your head (on paper). Well, you still need to be able to use the project search to find connections (definition of the called function, initialization of variables).
Maybe modern too.
Efficient work with legacy code
PS:
For me, my quiet and efficient way is to surround part of the code with tests, and make changes. It saves nerves.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question