Code of honor

I want to write about one of the main things that make my developer life useful and interesting.
I noticed that most of the people with whom I had the honor to work were bound by a promise, a kind of unwritten “code of honor”. It doesn't quite look like a samurai bushido, so let me briefly describe it:

Code and Debt

• My work is a reflection of my skill. Personally, I identify this with quality.
• If I have committed myself to the project and the deadlines, then I will do my best to keep my word.
• It is a matter of honor to keep our promises. I am ready to make personal sacrifices to keep my word.
• Obligations and sacrifices are purely voluntary and are guided only by internal motivation. Additional external pressure is considered a violation of the Code: I am already doing my job as well as I can.

Communication

• I openly admit if I don’t understand something.
• Subordination is not important in discussing technical details. The persuasiveness of the argument matters, not the speaker's position.

Asking for help

• My colleague’s time is no less valuable than mine.
• I carefully studied the documentation and FAQ.
• I am not afraid to ask questions if necessary. I carefully prepare my questions. If this helps my colleague, I will send the essence of the questions by e-mail.
• I take notes when they explain something to me and don’t ask the same questions twice.

Assisting

• I try to help my colleague who asks for my help as much as possible. It doesn’t matter where, in which unit and in which group he works.
• My help is limited only by the project load, or by the fact that a colleague began to go beyond.
• I try to simplify the use of my work by others as much as possible by documenting and structuring my code.
• Thus, I reduce the work of the person who will use my code, as well as my intervention if necessary.
• I support new employees both morally and professionally.

I began to adhere to this Code, mainly working at SAP AG in Waldorf. And yes, I think it is universal and not tied to one country or locality. So why am I writing about him?

In fact, this code is clearly aimed at responsibilities that can complicate your life. If you are the only one who has accepted this Code for yourself, you are doomed. Others will use your goodwill and your time. They will use it, which means that you will very soon abandon it.

On the other hand, when a group of people starts using it, everything changes dramatically. I was lucky to work in such teams, and in such cases I recognized my work as pleasant and useful. I felt support, and my working relationship was built on mutual respect and high motivation.

Will I expect everyone to always stick to it? No - we are all human beings and each of us attaches a different meaning to different points. I just wanted to write this Code as an example and recommendation.

I believe that in the future, the Codex will be able to significantly increase the efficiency and success of the company.

Let's reveal our strengths again!
Jens.