Bob Martin's Programmers Oath - What do you think?

PHP
1

I like it. :smile: http://blog.cleancoder.com/uncle-bob/2015/11/18/TheProgrammersOath.html

The Programmer’s Oath

In order to defend and preserve the honor of the profession of computer programmers,
I Promise that, to the best of my ability and judgement:

I will not produce harmful code.

The code that I produce will always be my best work. I will not knowingly release code that is defective either in behavior or structure.

I will produce, with each release, a quick, sure, and repeatable proof that every element of the code works as it should.

I will make frequent, small, releases so that I do not impede the progress of others.

I will fearlessly and relentlessly improve the code at every opportunity. I will never make the code worse.

I will do all that I can to keep the productivity of myself, and others, as high as possible. I will do nothing that decreases that productivity.

I will continuously ensure that others can cover for me, and that I can cover for them.

I will produce estimates that are honest both in magnitude and precision. I will not make promises without certainty.

I will never stop learning and improving my craft.

I suggested #10. I will always teach others to program well too, when I can.

Scott

2 Likes
2

I would add;

  • I will document my code with as much care as I write the code itself
2 Likes
3

Better would be to make it self documenting as much as is possible (since despite best intentions documentation - including comments in the code - are not always kept up to date).

4

From my perspective, it’s not a question of how it’s documented, so long as it is, and can then be followed once its originator has had a rather untimely encounter with the proverbial omnibus.

1 Like
5

omnibus?

On a more serious note - that the code is documented, I agree, is the important part. The idea that code can be completely self-documenting is ridiculous, as is the idea that every single method, or worse, line of code, needs a slew of comments to support it. If someone can look at your work and know what it does, and when relevant, why it does it? That’s what matters.

6

I’d like to see something like this as part of the Programmer’s Oath:

I won’t shy away from best practices like progressive enhancement and accessibility because they seem too hard or like too much trouble.

1 Like
7

I was led to believe

Always code as if the person who ends up maintaining your code is a violent psychopath who knows where you live.

Edit:

4 Likes
8

I think we may have to agree to disagree… :wink:

1 Like
9

Haha. Yeah, I’m going off of

560×733 20 KB

I didn’t see the second (dated) definition there :wink:

10

Probably because many of us fail to read things anymore

1 Like
11

If only Jeff also believed in writing software as if the person using your code is a violent psychopath who knows where you live. :wink:

1 Like
12

On the point of coding, I’d add:

I will do my best to program, so the code speaks for itself. If it can’t, I’ll help it with my own commentary.

Scott

1 Like
13

I thought you meant me for a second, then I realized the context.

Are you suggesting that @cpradio isn’t already a violent psychopath? News to me. :smiley:

1 Like
14

Wait people still think I’m nice? WTH!!

15

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.