Source code too complicated at the new company?
Hello,
I'm new to working as a software developer at a large company and this is also my first IT job.
I'm a little desperate right now. The code was extremely, incredibly complicated.
I understood the syntax of the code to a certain extent. I found the semantics and logic behind it very difficult to follow and understood very little. If I were tasked with implementing a new feature, I wouldn't know where to implement it in the code because the source code itself is very large.
Has anyone had the same experience and can give me some tips? 🙂
Thanks in advance.
(1 votes)
Loading...
You just have to go through that. Try to understand what happens when. You can also help one of the colleagues, or there are meaningful comments in the code (if you are lucky).
But that also happens to a confessed software developer again and again that he sits in front of code where you never have to touch him.
Especially when the code has been adjusted by the same programmer over 20-30 years and is now retired and no one can understand his thoughts.
Welcome to the “software development”, the whole thing is not bad at all and even completely normal!
Imagine the whole thing like a book.
No one can read and understand a book/program with more than a thousand pages/code in a few hours!
Especially if it is code with redundancy etc.
Take your time to understand the code slowly.
Ask employees if you are not aware of methods.
This problem will always accompany you in the IT!
For example, if you need to write the code in another language or there is a new framework.
Every major software project is difficult to digest. However, if the code is still “organically grown” (i.e., it has not been built according to any clear guidelines or has been extended without system), this is much more difficult.
Normally, you should be able to contact an experienced employee who helps you. Ideally, there are also documentation on code organization and architecture so that you have a rough idea what, where, how and why was done.