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, some kind of unwritten "code of honor." It does not quite look like the samurai Bushido, so let me briefly describe it:

Code and duty

• My work is a reflection of my skill. Personally, I identify it with quality.
• If I have committed myself to the project and the deadline, then I will do my best to keep my word.
• This is a matter of honor - to fulfill their promises. I am ready to make personal sacrifices to keep my word.
• Obligations and victims are purely voluntary and are guided only by intrinsic 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 confess if I do not understand something.
• Subordination is not important in the discussion of technical details. What matters is the persuasiveness of the argument, not the position of the speaker

Asking for help

• The time of my colleague is no less valuable than mine.
• I have 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’m emailing the gist of the questions.
• I take notes when they explain something to me and do not ask the same questions twice.

')

Assisting

• I try to help the colleague who asks for my help as much as possible. No matter where, in which division and which group he works.
• My help is limited only to the project load, or the fact that a colleague began to go beyond.
• I try to make it as easy as possible for others to use my workings, 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 Walldorf. And yes, I think that 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 duties that may complicate your life. If you are the only one who has adopted this Code for yourself - you are doomed. Surrounding will enjoy your goodwill and your time. They will use it, which means you will very soon abandon it.

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

Would I expect everyone to always stick to it? No - we are all human 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 data the Code will be able to significantly improve the efficiency and success of the company.

Let's discover our strengths again!
Jens