Dad and The Ten Commandments of Egoless Programming (2012)

272 点作者 dodders大约 10 年前

18 条评论

greggman大约 10 年前

> Critique code instead of people – be kind to the coder, not to the codeA fellow co-worker taught me by example to try to always phrase each code review comment as a question.Instead of> This loop never terminatesWrite> Does this loop terminate?Instead of> There's no test for this conditionwrite> Is there supposed to be a test for this condition?I'm probably not thinking of good examples but for some reason, more often than not, the direct comments came across as "you screwed up!" where as the questions instead made it feel like I was discovering my own mistakes rather than have someone tell me I made one.It's probably subtle and maybe some people will think it's dumb but I really appreciated it. It felt like it went a long way toward me feeling like saw my own mistake and fixed it before I checked it in instead of the direct approach which made me feel stupid and embarrassed.I've tried to adopt that approach (though it's a struggle to remember to apply it).

评论 #9204197 未加载

评论 #9204147 未加载

评论 #9204550 未加载

评论 #9204295 未加载

评论 #9205090 未加载

评论 #9205307 未加载

评论 #9204174 未加载

评论 #9204149 未加载

评论 #9205631 未加载

评论 #9204816 未加载

评论 #9208688 未加载

评论 #9204627 未加载

评论 #9204961 未加载

pjmorris大约 10 年前

Always good to see Jerry Weinberg's work mentioned. I tried reading 'The Psychology of Computer Programming' when I was in college, it didn't grab then. Finally read it 15 years later, and realized that the material there would've especially helped in my first couple of jobs.Also... my dad was 45 when I came along. I didn't get to spend much time with him before he was gone, but every moment was valuable and is cherished. I still try to make him proud, and suspect your dad would be proud.

danso大约 10 年前

The best part of this list is that with some tweaks, the commandments can pretty much apply to any field of personal and professional pursuit.One rule I might add (and one that is also easy to apply elsewhere): Remember that far more time will be spent reading your code than writing it.Grokking this not only has practical implications for how you write code (suddenly, the importance of style guides becomes clearer), but it makes you realize that this is how projects get built: programmers re-using libraries that contain encapsulated, clear functionality. Realizing that someone has to read your code -- even if that someone is mostly just you -- requires a modicum of empathy...and more often than not, this aids in the design process.A common complaint about learning via something like Codecademy is that you might learn the syntax and how to solve problems...but you don't get much guidance on how to apply that knowledge to real projects. I think part of this is because with Codecademy, you're only writing code for the auto-checker to compile and test. Once you start writing code for humans to comprehend and re-use, it becomes easier to see how code becomes a real-world project.

greenyoda大约 10 年前

Jerry Weinberg wrote those "commandments" in 1971. (It's sad that the article gives a link to his book but never mentions his name.) It's interesting how well they've kept their relevance over the years, despite the huge changes in the practice of programming. However, we who do the programming still keep on forgetting these things and need to be periodically reminded of them.

mfisher87大约 10 年前

I have these on display at my desk. I've always wanted to know how to encourage cultural adoption? What are the arguments against these rules? There must be some.My reasoning about these rules is that they derive from the idea that as teams of programmers, we're professionally motivated (and being paid) to produce the highest possible quality results. To that end, these rules compensate for human biases and faults to maximize quality.Many of the practices you've read about some companies enforcing, such as "there are no bad ideas" or "no stupid questions" can be related back to these rules under the same reasoning. None of us do a perfect job of compensating for our human faults and biases, so some rules help to improve our performance.My dad also passed away very early, soon after I finished college, and I credit him for making these rules so easy to follow.

评论 #9205995 未加载

sporkenfang大约 10 年前

When I read things like this, it strikes me particularly that my dad is one of those rocket people the author is talking about. I'm glad he's done what he has to put things in space so that maybe someday people can go places other than the Earth on a slightly more than part-time basis.All dad-boosting aside, this is a brilliant list, and I'm glad to have it, OP!

Animats大约 10 年前

The trouble with egoless programming is that you don't get promoted.

评论 #9204204 未加载

评论 #9204583 未加载

评论 #9204637 未加载

评论 #9204250 未加载

评论 #9205558 未加载

评论 #9204759 未加载

评论 #9204779 未加载

dllthomas大约 10 年前

'No matter how much “karate” you know, someone else will always know more.'As stated, there is always at least one person for whom this is not true. However, even for such a person it is likely the case that there are still people who know things they don't, and the rest of 3 continues to hold:'Such an individual can teach you some new moves if you ask. Seek and accept input from others, especially when you think it’s not needed.'

Almaviva大约 10 年前

Am I really that rare that I treasure people above all others who will speak to me directly if they don't like something?With the themes in this article and others like it, are they how you should behave if you want to meet your own goals, or about how people you're subordinate to prefer you behave, in order to not rock the boat too much?

评论 #9204391 未加载

评论 #9204316 未加载

评论 #9204647 未加载

a3n大约 10 年前

I agree with everything on this list, but in case someone takes things too literally, I would change this:Fight for what you believe, but gracefully accept defeat.to this:Advocate for what you believe, but gracefully accept defeat.Sometimes "fighting" for what you believe can turn in to just fighting.

datashovel大约 10 年前

Great list.When I first became involved in programming as a career, I got this unexpected and uneasy impression that people in the industry (extrapolated from my real-world experiences early in my career) were generally passive aggressive about how they handled conversations about code and how they agreed or disagreed with others about how the code should "be". I think those groups of people would have benefited greatly from this list. Simultaneously it would have prevented alot of the angst I experienced as a young developer.

toolslive大约 10 年前

'''Don't feel a "winner" when having corrected, don't feel a "loser" when having been corrected, and banish all feelings of mutual competition.''' <a href="http://www.cs.utexas.edu/users/EWD/transcriptions/EWD06xx/EWD683.html" rel="nofollow">http://www.cs.utexas.edu/users/EWD/transcriptions/EWD06xx/EW...</a>

UserRights大约 10 年前

A little late to the party, but I would like to ask:is there still some research going on in the areas of psychology and programming? Not AI, but how the state of the programmers mind affects collaboration, the quality of the code and the general outcome of projects?Any hints and links would be very appreciated, thanks!Have a nice sunday!

phprocks大约 10 年前

Highly recommend picking up the book (The Psychology of Computer Programming)I have a low attention level, and one of my favorite things about this is you can really jump around and pick up the chapters from anywhere.Also despite the title of the book, its actually a very light and entertaining read.

kbwt大约 10 年前

This has been posted before. A moderator might want to add (2012) to the title.

评论 #9204199 未加载

pvaldes大约 10 年前

I came here only for the promise of elves typing a keyboard at superfast pace...

digi_owl大约 10 年前

Something for everyone in that.

raverbashing大约 10 年前

It seems to me this list, while having positive ideas, reeks of condescendence. it's mostly about how you are "much better than everybody, that's why you have to play cool with everybody"What is missing is a healthy dose of "why do you think your ideas are better than everybody else's?"Readability is mostly subjective. Code quality, maintainability, etc, are mostly subjective as well.So don't give me that BS "I'm just trying to get the best code possible" when it's your opinionSure, I'm not saying that something like xx = strinvcatpfr(yy * zky_eng) can't be improved, but beyond a certain point it's mostly about taste and endless nitpicking

评论 #9204158 未加载

评论 #9204556 未加载