5
Deniii
6y

All summer I've been working at a company doing some full-stack development. Starting my last year in university, I really wanted some real life experience that ties into my studies.

I did not expect to find horrible, undocumented, code that has been written 5 years ago, where the senior developer who wrote it doesn't even know what it does. The worst part? They are STILL not documenting! I tried to document, but got this in return "you don't have to document everything. Especially if it is understandable". But they don't even understand their old code!

Monday morning, we had a meeting and they asked what I thought of working here, seeing as I am done this week. I respectfully told them that their code is not readable, and it will make it hard for new employees to understand. The boss in return says "you're the third newly hired employee this summer to say this... Maybe we do have a problem then"..

No shit. Please for the love of God, comment your code!

Comments
  • 0
    Or even better make the code clean so it doesn't even need comments most of the time. Paper documentation tends to grow out of sync with the actual code implementation pretty fast. So readable self-explanatory code is the way to go in the long run.
  • 1
    @pieteckhart I agree with this. Sadly many people still do not write explainable code. Today I saw this function "switchX()". And as far as I know, the code is pure magic because nobody understands it.
Add Comment