-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is pride and diligence really required? #59
Comments
As an atheist, I don't see the relevance of 'Deadly Sins' to the argument. More practically, "Taking pride in ones' work" has a very different meaning to "being Prideful". It means a dedication to doing ones best. Is this a case of interpretation? |
Yes. If you ignore the "deadly sins" aspect I think my comment still stands: colloquial interpretations of the word "pride" are at odds with humility. If you mean a dedication to quality, or any of the other synonyms I listed, say that. Many societies have weird toxic ideas around pride and diligence. |
Larry Wall says there are three great virtues of a programmer: Laziness, Impatience and Hubris.
Reducing the oaths down to one or two words may help one remember them, but just like saying laziness, impatience and hubris are virtues, mean can be lost or confused. |
Wow, I hadn't realized that pride and diligence were such loaded terms across different cultures. To be clear, the sentiment underlying this tenet is effectively: "I will do a good job." Maybe that should be the wording of the tenet. What do y'all think? Too plain/lacking nuance or just right? |
I'd go with something like "Do what's necessary to ensure high-quality work." I notice quality is mentioned in other issues, maybe this can be wrapped into that. At the end of the day these are all elaborating on "be good, not bad," so figuring out what it is we're really trying to communicate and whether these are aspirational, or enforceable standards, would be good. Quality is subjective. But where I'm from at least ensuring quality won't be misinterpreted as forming industry cliques or working yourself to death... |
How about: I will be diligent and take ownership of my work's flaws as much as I do its feats. |
Right now for me that would potentially mean doing hundred hour weeks with no additional compensation. I can't feasibly sign any oath that requires me to do my utmost to ensure quality, because sometimes the reality of business means that quality has to be sacrificed in the short term. At the end of the day, I can't see why being diligent and taking pride in our work is a bad thing. I could understand pride in isolation being considered bad, but to take pride in one's work to me is to put yourself into what you do, and to hold yourself to a standard. |
I know the thread might be all-done, but fwiw: Completely agreed. |
I don't see it in the Hippocratic and I have the same problem with its mention in the Engineer's oath. Pride is the first Deadly Sin, it can inspire some positive things but also some negative things. Seems to me that its function is to foster a guild mentality more than anything. Pride is at odds with humility. Diligence by itself without clarification could merely be interpreted as "working long hours" which is not positive thing about our industry. Being programmers, perhaps a definition of terms like "X at least Y but not to exceed Z" would be a more effective behavioral guide to the sorts of people who need an oath to follow.
Seems to me that the existing oath covers:
So as implied, I would suggest replacing number 8 with some of the words I used (taken from a generic list of virtues, where pride is notably absent.) Diligence is defined by that list as "Conscientiousness in paying proper attention to a task; giving the degree of care required in a given situation. Persevering determination to perform a task." maybe including it with some of that elaboration would be more useful. (America has a Puritanical "hard joyless work is a virtue" history, whereas other countries prioritize other things over work; making this strike a balance and be universally applicable to all programmers would be valuable. I find the definition of "diligent" to be okay, it's just a word that apparently gets misused often.)
The text was updated successfully, but these errors were encountered: