The Programmer's Oath
-
My programmer's oath: 1. I will work not work with Ruby or other duck-typed, runtime-typed, or "script kiddie" languages. 2. I will not work with people that work with #1 3. I will code when my brain feels like coding, I will not code on YOUR timeframe 4. I will not work in a cubicle. 5. I will not put up with shitty equipment and stupid management decisions 6. I will write code that is maintainable, extensible, commented, and documented, no matter what management says. 7. I will spend time testing my code, but YOU damn well better have a people, resources, and the commitment to test my code independent of me. 8. I will write code using my own well thought out architecture, not some fly-by-the-seat-of-your-pants Agile methodology bullshit. 9. I will not waste my valuable time learning some half-ass open source latest rage just because every other idiot says it's the latest rage. 10. I will always have time to work on my own stuff because frankly, it's usually more interesting than the crap project I'm working on that actually pays the bills. So yeah, there you go. Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
:thumbsup: I like yours better than his, except maybe the first one. My life is JavaScript these days.
TTFN - Kent
-
:thumbsup: I like yours better than his, except maybe the first one. My life is JavaScript these days.
TTFN - Kent
Kent Sharkey wrote:
My life is JavaScript these days.
Javascript is the exception because you just have to code in it to do web stuff. But actually choosing to use Ruby, Python, or PHP? Ugh. However, choosing to use Javascript with node.js is another WTF for me. To the tune in Rocky Horror...I'm just a sweet anachronistic anarchist. ;) Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
-
Clean Coder[^]:
In order to defend and preserve the honor of the profession of computer programmers...
Eh. Worked on my machine.
I will not use
if - elsestatements to make my code work differently in test and production modes. -
My programmer's oath: 1. I will work not work with Ruby or other duck-typed, runtime-typed, or "script kiddie" languages. 2. I will not work with people that work with #1 3. I will code when my brain feels like coding, I will not code on YOUR timeframe 4. I will not work in a cubicle. 5. I will not put up with shitty equipment and stupid management decisions 6. I will write code that is maintainable, extensible, commented, and documented, no matter what management says. 7. I will spend time testing my code, but YOU damn well better have a people, resources, and the commitment to test my code independent of me. 8. I will write code using my own well thought out architecture, not some fly-by-the-seat-of-your-pants Agile methodology bullshit. 9. I will not waste my valuable time learning some half-ass open source latest rage just because every other idiot says it's the latest rage. 10. I will always have time to work on my own stuff because frankly, it's usually more interesting than the crap project I'm working on that actually pays the bills. So yeah, there you go. Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
Yowza, what you said, Brother !
«I want to stay as close to the edge as I can without going over. Out on the edge you see all kinds of things you can't see from the center» Kurt Vonnegut.
-
Clean Coder[^]:
In order to defend and preserve the honor of the profession of computer programmers...
Eh. Worked on my machine.
Well, I vote for Marc's version of the oath(s). But, if I had to add one additional "commandment" to the impossible-to-attain-ideals set forth in the linked-to article: 10. I vow to do whatever it takes to make sure I am fully compensated, my person and intellectual property rights are treated with respect, and that I am paid on time.
«I want to stay as close to the edge as I can without going over. Out on the edge you see all kinds of things you can't see from the center» Kurt Vonnegut.
-
I will not use
if - elsestatements to make my code work differently in test and production modes.Doesn't that also prohibit using mock objects in testing?
-
Doesn't that also prohibit using mock objects in testing?
No, does not prohibit that. Should have added: '... and thereby be the cause for penalties worth billions of Euros'. Because, the ultimate blame for this recent emission test fiasco fell on a couple of 'software engineers', aka programmers.
-
My programmer's oath: 1. I will work not work with Ruby or other duck-typed, runtime-typed, or "script kiddie" languages. 2. I will not work with people that work with #1 3. I will code when my brain feels like coding, I will not code on YOUR timeframe 4. I will not work in a cubicle. 5. I will not put up with shitty equipment and stupid management decisions 6. I will write code that is maintainable, extensible, commented, and documented, no matter what management says. 7. I will spend time testing my code, but YOU damn well better have a people, resources, and the commitment to test my code independent of me. 8. I will write code using my own well thought out architecture, not some fly-by-the-seat-of-your-pants Agile methodology bullshit. 9. I will not waste my valuable time learning some half-ass open source latest rage just because every other idiot says it's the latest rage. 10. I will always have time to work on my own stuff because frankly, it's usually more interesting than the crap project I'm working on that actually pays the bills. So yeah, there you go. Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
Damn I finished the space in the signature. I'll have to put this in my bio.
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver "When you have eliminated the JavaScript, whatever remains must be an empty page." -- Mike Hankey "just eat it, eat it"."They're out to mold, better eat while you can" -- HobbyProggy
-
No, does not prohibit that. Should have added: '... and thereby be the cause for penalties worth billions of Euros'. Because, the ultimate blame for this recent emission test fiasco fell on a couple of 'software engineers', aka programmers.
Avijnata wrote:
this recent emission test fiasco fell on a couple of 'software engineers', aka programmers.
Logical, they not have the $$$ of the managers to buy allibies ;P
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
My programmer's oath: 1. I will work not work with Ruby or other duck-typed, runtime-typed, or "script kiddie" languages. 2. I will not work with people that work with #1 3. I will code when my brain feels like coding, I will not code on YOUR timeframe 4. I will not work in a cubicle. 5. I will not put up with shitty equipment and stupid management decisions 6. I will write code that is maintainable, extensible, commented, and documented, no matter what management says. 7. I will spend time testing my code, but YOU damn well better have a people, resources, and the commitment to test my code independent of me. 8. I will write code using my own well thought out architecture, not some fly-by-the-seat-of-your-pants Agile methodology bullshit. 9. I will not waste my valuable time learning some half-ass open source latest rage just because every other idiot says it's the latest rage. 10. I will always have time to work on my own stuff because frankly, it's usually more interesting than the crap project I'm working on that actually pays the bills. So yeah, there you go. Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!
Marc Clifton wrote:
I will always have time to work on my own stuff because frankly, it's usually more interesting than the crap project I'm working on that actually pays the bills.
:thumbsup::thumbsup::thumbsup::thumbsup::thumbsup: